Best Practice? Change a secondary xml input data source. startup

[Bob C.]

Reading the 5 part blog (link below)... approach to programatically modify
the Infopath .xsf file.

Would this be a best practice / pattern for getting xml from outlook
(contacts?); open an Outlook conact, edit InfoPath(IP) form of contact data;
save to SQL db; rinse; lather; repeat ...

As suggested by: Modifying InfoPath manifest.xsf file from script (1/5) at
http://blogs.msdn.com/infopath/archive/2004/05/04/126147.aspx

 

[renee rieser]

Messing with the manifest...Double Ick.

You're in over my head but, FWIW, I would be looking at modding the
secondary xml source from inside the on-load event handler.

 

[jgmeyer]

You would expect that using examples from the official InfoPath blog would be
best practice, but I would be very careful. Messing up the manifest can
render the form unusable.

 

[Bob C.]

I managed to make progress using an xsd as the main source for my IP form.

I initially created an IP form from an xml doc created by my Outlook addin.
Next, I used the "Extract Form Files..." which provided an .xsd for me to
look at.

I now jump between my xml editor (Stylus Studio), and Infopath. I use
Stylus to add new elements to my xsd, as it is esier to use than VS2005's
schema tool. I use infopath for the general layout steps.

Definately use sp1.