-
The only way to write business logic for the browser-enabled forms is by doing it in .NET (it will get executed on the server). Forms developed this way will seamlessly work both in the Forms Server and the rich InfoPath client.
However, although there is no direct way to run Javascript from a browser-enabled form, you can host your form in a ...
-
Hmm... this is strange... if you are running full-trust and the file is accessible, I am not sure what else could be wrong.
One thing you could try is to use the FSO object to load the file as text. Here is an MSDN example that shows you how to do this: http://msdn2.microsoft.com/en-us/library/t58aa4dd.aspx
If you can get the XML in this way ...
-
Couple of ideas:
1. There is a problem with the certificate and so the form is not *really* running as full trust. To check this, try to run Application.Quit() from your code - if this fails, the form is not really executing as full trust
2. The file is not accessible so you get a true "access denied" (this is less likely, I think ...
-
Hmm... how did you set your form to be full-trust? How are you testing it? If you are using IP2003, you cannot preview in full-trust so that could be your problem.
-
A good thing is to check the server logs to see if there are more details about the unknown error you are seeing.
Forms Server uses the SharePoint log files (typically located under %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\12\LOGS) with Area="Forms Server".
-
-
Hmm... since I am not seeing the data I cannot say what is going wrong. One guess is maybe you should try to change the underlying data type of DateOfInspection to DateTime from Date, and then you can tell it not to display time. If that does not work I don't know what will :)
-
You can read any XML file the same way, whether or not it's included in the form:set xmlDocument = XDocument.CreateDOM()
xmlDocument.async = false
xmlDocument.load(pathToYourFile)set xmlDocument = XDocument.CreateDOM()
xmlDocument.async = false
xmlDocument.load(pathToYourFile)Important note:
If pathToYourFile points to a ...
-
Application.Quit() is what you're looking for. However, it requires your solution to be Full-Trust (for obvious reasons, you will really be shutting down InfoPath). Application.Quit() takes an optional bForce argument:
bForceOptionalBooleanDefault value is False. Determines whether open forms will be saved during the quit operation. If set to ...
-
Interesting... I would like to take a look at your Solution, do you think you could share out our XSN? You can attach files in the Files section on the forum...