InfoPath Dev

Clayton can you post the rules or whatever you use for your "back-end validation method" to disable your submit button until all required fields are completed...  I am having problems in Web Forms with the "cannot be blank" popups getting in the way of people being able to select option buttons.  Also the posting ...

 Thanks for this Jimmy. I got the insert command to work but have to run to a few meetings -  when I get back I will try the rest. I really appreciate the help!

Now why didn't I think of that? Thanks so much, works like a charm! 

You'd have to try it, but I think you could publish the form as a content type including all of the fields that you want promote.  Add that form as a content type to the form libraries where you are submitting, and remove the fields that you don't want displayed. 

[quote user="Hilary Stoupa"] I think I'd add another field (True / False, default to false) and add a rule to my button that I'm using for my query to set that field to True -- then you could hide your data fields section if that field was not equal to true.[/quote] Success on one of the things that I needed!! I was able to ...

This error makes it sound as if the data connection to the Qdabra Rules XML file that is injected as a resource was converted. Open the Data Connections dialog, and select QdabraRules and click Modify. When you get to the step where the file location is indicated, click the Resource Files button and select the QdabraRules.xml resource file. If ...

I have created a browser enabled from in InfoPath 2007 that is linked to a form library. I only promoted half the fields on the form to be viewed in this specific form library. What I need to be able to do is send/promote the remaining fields on the form to a different form library. I’m a novice to InfoPath, so I’m not sure if this is possible. ...

What if you gave each row a hidden isReadOnly field with a default value of false, and set this field to true when the form is opened, then use that to control the conditional formatting?  That should work.

I have a repeating table, that each time the form is saved (the form will be opened and updated repeatedly) I want the existing rows in the repeating table to become read only when the form is opened again and only the newly added rows to be editable.  I tried adding a date/time value to the repeating table and comparing this with a ...

Ok, suppose your main data source was structured like this: myFields   L  attendees        L  attendee (repeating)               L name (string)               L attended ...