InfoPath Dev

I have developed a from in InfoPath 2007 that has some dropdowns that get information from access tables.    The form works well for me, but there are security issues when others try to open it.   They can generally get past them (looking for a smart card), but they cannot get ALL the information that is coming from ...

I'm glad it's working. I guess my last remaining question is how you ended up with an injector that said qRules v4.1 but without that field in your form. I know that some beta versions of qRules v4.0 were sent out, so I wondered if you were one of the recipients. Thanks.

Hello,   I'm having a problem, I'm trying to create infopath form that has a date picker which I can pick a date thats pulling from sharepoint calendar and displays that days events. I want the results pulled into a repeating table. I've tried and it kinda of works but i'm only getting a few events listed from the ...

I did download the 4.1 Trial and installed it [Embarassed by my "rookie mistake" above]. As a quick fix, I put that into a checkbox on the form - Ernesto, I'll do what you suggest in a later iteration. With qRules 4.1 in-place, the submit worked, and I think I'm on my way!  Thanks everyone for your expertise, and patience.

 I'm having a problem with one of my users not being able to save updated InfoPath to Outlook. Basically, a user submits an InfoPath to the in-box and the reviewer works the question that was asked. Once the reviewer adds their response, the form needs to be saved for exporting purposes. The Problem: I have a button set up to click ...

All the fields,  JanP...DecP and the dropdown"personnel are in the repeating field. 

Yeah created a temp field but as soon as I drag it into the repeating table it takes on all of the same properties as the existing field. Is it normal for a all of the properties to be greyed out on a sharepoint calculated field in a repeating table? It's the same in all of my forms that use calculated columns in sharepoint lists :(

Bummer :( Did you try creating a "temp" field and setting the default value to the calculated value?  Then you can format the new temp field with the proper decimal settings.  If you don't want the extra field, you can try a calculated value and see if you get the format options there.

This sounds like a pretty basic workflow scenario.  There are a few out of box approval workflows that might be useful for you to at least start as a base and then expand on it as needed for your scenario. For more information, I've included links to a few articles that will hopefully get you ...

The format button is greyed out because it's a calculated field in a repeating table.