InfoPath Dev

Qdabra's DBXL can handle your scenario. It would also mean you wouldn't have to redesign your form. I do not know of a way in InfoPath to take a form that has been based off an XSD and change it to using a database as its main data connection -- I think in order to do that, you would need to start over on your form. May I make a ...

It is always really hard to pick up and come to terms with a project someone else has left behind -- I understand your frustration. I guess I am kind of curious why the form wasn't just based on the db to begin with -- when you create a new InfoPath form, you have the option to base it off a db and then (depending on the types of fields in the ...

Did you look at the xsd you created with Visual Studio to see if the xsi:nil attribute was on the elements that you'd like to be able to leave blank? I'm just curious if that is indeed what happened in the creation of the schema. Keep in mind, the blog post I referenced is from 2005, things may have changed since then. Is your intent to ...

Hi: That information is in the file header. In the post at http://chrissyblanco.blogspot.com/2006/07/infopath-2007-file-attachment-control.html about halfway down the code, the author pulls the file name from the attachment and converts it from bytes to a string. When I tried using this code (modifying only the location it saves a file to, ...

Hi: I think you'll need to modify your XSD so that the elements that you want to allow nulls on have the attribute xsi:nil = "true". While this post is not entirely to your issue, it does have some information on the xsi:nil attribute: http://kjellsj.blogspot.com/2005/04/submitting-xsiniltrue-values-from.html as does this ...

I am so happy you have your form working the way you want! As far as submitting your rows to a SharePoint list, you could first set up a data connection to the list, then, in your code, set the data fields in the list to the values you want to submit, and submit. I am not sure of the syntax, but here is a link to the InfoPath Developer Reference ...

Well, the type mismatch is because your second line is selecting a node, and then you are trying to set a text field to a node... thus, they are not the same type. I am pretty much stumped at this point -- I had thought your problem would be due to the xpath ("EmployeeName_Full") being incorrect, but really, since your first block of ...

Okay, they are attributes. Try this "@EmployeeName_Full"

Are you using IP 2007? Could you rightclick EmployeeName_Full and copy the xpath?

Beautiful! Glad you got it!