InfoPath Dev

Ah: Main reason for this issue is, whenever a data field that is bound to your ActiveX is changed, InfoPath destroys your control and create a new one. This is mainly because InfoPath has to apply your view xsl to your data source to create the view you see on the display. Every time data source changes, InfoPath re-applies the xsl file and ...

I'm new to COM and have been working on a custom InfoPath control.  It's written in C#, implements the InfoPathControl interface, and generally works as expected  - Yay!  Sometimes, though, InfoPath "re-instantiates" the control.  It usually happens in response to ValueChanged events when the new value is not ...

As far as I can tell, there is no way to do this.  It seems that the only thing any code bound to a form or wrapped inside a control has access to is the data model, made available as a DOM supporting XPath queries.  If there's any way to refer to controls on the form rather than the data they're bound to, I'd be happy to ...