InfoPath Dev

Here are a couple examples: Sub msoxd_my_field1_OnValidate(eventObj) dim errObj set errObj = eventObj.ReportError(eventObj.site, ''Short err message text'', false, ''long err message'', 1234, ''modal'') 'or if not using returned error object (also default value for 'bstrDetailedErrorMessage' and 'lErrorCode' missing args) eventObj.ReportError ...

Try storing the return value of resources.GetObject(...) to see what is being returned. It might help determining what's going on. Jim Cantwell InfoPathDev - Redmond

It sounds as if your project file may be corrupted. I recommend creating a new InfoPath solution, add a reference to the dll, and make sure Copy Local is True. Then publish the form, a blank form is sufficient, then check the xsn file to verify that it contains the dll. You can quickly view the xsn contents by changing the .xsn extension to .cab ...

The 'File or assembly name SSInfopath, or one of its dependencies, was not found' error is most likely from the assembly not being in the xsn. If the form assembly is referencing this dll, it must reside in the .xsn or be installed in the GAC. In Visual Studio, check the 'Copy Local' property for the dll reference and make sure it is set to ...

'Template' is referring to the .xsn file created by InfoPath. The form file is usually referring to the .xml data file which is linked to the template. When you publish a form to sharepoint, you are creating a document library. Under the document library will be a Forms/template.xsn file, which is the form template. This form template is ...

What particular security exception are you seeing? And is your form digitally signed with a trusted root certificate? Jim Cantwell InfoPathDev - Redmond

With XP using IIS5.x, use the Application Protection option on the 'Home Directory' or 'Directory' tab in the website properties pages. If you configure for ''Low (IIS Process)'', the SYSTEM account is used, and you will need to give the SYSTEM account database access (assuming the DB is on the same machine). Jim Cantwell InfoPathDev Redmond

The SmartCombobox does not bind to a repeating node. Binding a property to a repeating node requires the value property be an IXMLDOMNode which is a very limited set of controls. The smartcombobox writes multiple values into one property, which can be parsed if necessary. Jim Cantwell InfoPathDev Redmond

The SmartComboBox will have similar behavior to the regular combobox with these additions: 1) Multiple selection support The value property will return the code values separated by spaces. If codes have spaces, then quotes will delimit the values. Example: Dataconnection: States Entries: /States/State ...