InfoPath Dev

I'm having an issue with preventing form submission where such submission bypasses the custom form validation I've written. I've disabled the Submit button on the toolbar and the only method of submitting the form normally is using a button with .NET code behind it. However when viewing the form, if the user closes InfoPath, they are prompted ...

Just in case anyone else is effected by this problem, I can offer a solution that I received from the kind people at Microsoft: Delete the temporary internet files of the effected user. This works. :)

A small subset of users are reporting the following error when opening an InfoPath form deployed on a local intranet SharePoint forms portal: ''Insufficient Security Privilege This form cannot be opened because it requests domain security level and is only allowed restricted security level. Contact the form author to resolve the issue.'' The ...

I'm only using the one form with my K2.net workflow. The latter half of the thread linked below describes why I have to republish the form:http://forum.k2workflow.com/viewtopic.php?t=232 I don't think it's the republishing that's at fault. I just wanted to demonstrate the even with no schema changes the form is incompatible with a previous ...

Thanks again, vt_asparagus. To try to answer your questions: I can preview my own form without encountering this problem (although prior to integration with K2.net I obviously can't submit the form as the functionality hasn't been added yet!). I wasn't making any changes to the InfoPath form's 'data source' - the last change was purely a ...

Apologies for hoggin' my own thread. :) On the Form Options dialog, using the Advanced tab, if I change the ''On version upgrade'' option to ''Do nothing (existing forms may not work properly)'' then older versions of the XML files work fine, just as long as the data source hasn't changed.

Okay, I may be having a 'moment' here but I've found that if I hack the XML files produced by the form, and update the older version to have the same version number it will open successfully. Presumably this won't work if the data source is actually different?

The following problem arises when publishing a revised form to a SharePoint document library. I'm using K2.net but perhaps someone here has experienced a similar problem... calling vt_asparagus! :) I've found that if I make a change to an InfoPath form and publish it to SharePoint, then any existing documents can't use the new version of the ...

Sorry for the delay in replying. I've tested both options and I'm pleased to report that the first suggestion of using OnContextChange works. The second suggestion fails when using thisXDocument.View.SelectText because even with the call to thisXDocument.View.ForceUpdate the field isn't yet part of the view. Thanks for your help in solving ...

David, If installing a client application (InfoPath) is a major concern for your project, then consider using K2 in conjunction with K2 SmartForms. These are basically ASP.NET pages which allow you to directly manipulate the data used by the workflow. Just my 2p, David