InfoPath Dev

With lots of help from Andrew May's WebLog, I figured it out. Here are some ...

I have about 9 InfoPath 2007 forms (not browser-enable) that are submitted to the same SharePoint Server 2007 Forms Library. Each form has a set of promoted properties, including ones like Client Name and Client ID. The problem is that each property is added, so I end up with 9 Client Name properties and 9 Client ID ones, and of course I want only ...

 I created the first version of the dataset using the wizard, then made some changes using the wizard, then made some more changes using the wizard. The last change was for it to use foreign keys and enforce data integrity. But, the wizard didn't actually implement the foreign keys. Then I re-created the dataset from scratch using the ...

 Nope. The ADO.NET dataset tracks inserts and deletes and then when you submit the form via the web service the ADO.NET dataset is synced to the database.  What I found out after much banging of my head against the wall was that the Visual Studio 2005 wizard that helps you define an ADO.NET dataset doesn't always handle changes ...

The "Choice" group is automatically inserted when you use an ADO.NET dataset. I'm not quite sure why. It is not "Choice" like a radio button. I have the same problem and it's a quandry. My ADO.NET dataset includes the primary keys for the tables that make up the dataset and, of course, they can't be null in SQL ...

I was trying to append rows to a table in code and kept getting the dread "Schema validation found non-data type errors" error. It wasn't the nil error and it wasn't caused by children being out of sequence. The main data source was somewhat complex: formFields     groupField1        ...

 Greg,     Just to make sure, I created a new form, added a time field, set the default to 0:00, showed it in a text box, and it displayed 12:00:00 AM. I added two Expression Boxes that showed the field, one with time format and the other with text format; the time formatted one showed 12:00:00 AM and the text one showed ...

I had several time fields that I changed to text. When I entered "1:23" into one of the text fields, it showed "1:23", but an Expression Box view of the field showed it as "1:23:00". Apparently something within InfoPath was still treating it as a time field. Deleting the old fields and creating new ones from scratch ...