InfoPath Dev

Hi-- I don't know the answer to your second question, but as to your first, I believe you need to change the postback settings for the text boxes. Under the text box properties, you'll see a Browser Forms tab. Try setting Postback to Always.

You'll want to open the form in design mode and check for the field that is mentioned in the error. Look in the data source task pane at your main data source and see if you can find the field. It may be marked as 'cannot be blank' yet isn't on the form where the user can fill it out, which can cause errors like this. Also, you ...

Hi: I've attached a simple sample to this post. Right click the link in the post header, save the file locally, open in design mode and preview. There's an expression box that uses position() to give 'line numbers' and a repeating table for the items. Of course, this means the user has to use the 'insert' widget to add ...

Hi: In the InfoPath menu bar, try "Tools / Go To Next Error". If the field in question isn't on the form, click the details button on the dialog box, and it will give you a message about what field is causing the problem.

Hi: I've attached a sample that uses conditional formatting to show / hide some expression boxes based on checkbox selection. To try it, right click the link in the post header, and save the template locally. Right click the saved template and select Design to open in design mode. Preview to see the functionality. Conditional formatting is on ...

Hi: It is your XPath in this line:  junk = oNode.selectSingleNode("/dfs:myFields/dfs:dataFields/d:Employee/d:EmpEmergContacts/@EmergFirstName").text You should use a relative XPath, like:  junk = oNode.selectSingleNode("@EmergFirstName").text

If you want to push the value from one form into a new form when you open a new form, you'll need to write code for it. IP doesn't handle this scenario out of the box.

Your code works in the client? Just not on the browser?

Hmmm. I'm not sure what you mean by opening the record from the view -- so, you save the record and leave the form open, then there is another view that shows all the records that the user can select from? When I searched the web for the error you were getting, I saw an old post on a Microsoft news group that suggested the primary key field in ...

You don't have the form ID set as the primary key for the child table, do you? Wait, I re-read your post, and you say you don't. You do have an ID column on the child table though, is that correct? I'm sorry, it really sounds like you have things set up correctly, so I'm a bit perplexed at what else to suggest.