InfoPath Dev

A related strategy that I have used is to set up a UI state document similar to this <view1 state="" someOtherState=""> <pane1 state=""/> <pane2 state=""/> </view1> Add the document as a Receive data connection. Despite the nature of the connection you can still write to ...

 Excellent! That's better than I had hoped for. Thanks, mate(s).

This relates to IP 2003. I have a form based on a schema complex enough that IP won't let me edit it in the datasource view. I really would not look forward to having to cut, paste, and rebind every control in the form any time I make a change to the schema. Is there a way to handle this more gracefully?

It sounds to me like you might want to break the workflow out into at least two operations. Use a list to select the record you want, then put your ddl in a detail view for the selected record.

 The SharePoint data connection specification (Tools -> Data Connections) allows you to control file naming.

I have a set of full-trust forms for which I need an efficient way to manage updates. Here is the setup. Source templates are stored on the server. Intranet users invoke a form instance from a browser by clicking a link that refers to the template by its urn (i.e. "IP.NewFromSolution("urn:foo:bar");"). The first time a user ...

Looks like my question was already answered here. Can't call a view switch on an OnAfterChange event. Amazing what you learn when you actually read the other posts ;)

(IP 2003). I have a ddl with values that correspond to view names. SwitchView is called based on the selection in the list. Here is the offending snippet:   function msoxd__Job_uglyHack.view_attr::OnAfterChange(eventObj) { var sChangedNode = XDocument.DOM.selectSingleNode("//d:Job/@uglyHack.view").nodeValue; if ...

 Thanks, Greg. I'll give that a try. When I've done some more testing I'll post back with the results in case anyone else runs into similar problems.  Cheers  

 Yes, I've tried that, and I'm stumped as to why the problem continues. I feel pretty confident -- based on the error -- that this is an InfoPath problem and not an Access one. But, when I have some free time I'll try building a simple one-table, 30 column mdb and see what happens.  In the mean time, if anyone else can shed ...