-
Not so random, updated to SP1 - the script now runs from the run command.
Now I just need to get the script to run from my asp page.
Thanks for all your patience.
-
Here is a random thought: are you sure that your production machine has InfoPath 2003 SP1 or later?
I believe InfoPath 2003 RTM simply does not expose InfoPath.Application
If you're running the RTM version of InfoPath then this is your problem
-
You can write code in your form to hide the task pane (use the OnSwitchView event handler in IP03). But then those that want it on, what do they do?
-
Unfortunately, no. That would be nice though.
However, there are some 3rd party apps that might be able to do what you want. Look at the section called "Web Form Conversion" at the bottom of this resource page: http://www.infopathdev.com/content/Internet.aspx
-
It runs but fails on this line:
var oApp = new ActiveXObject("InfoPath.Application");
With this error:
Automation server can't create object
-
When you are dealing with optional / repeating sections, their commands “bubble up” the dom tree of other sections they are contained in.
So if you have a section bound to a root node, and inside that you have an optional section, the section bound to the root node will receive the bubbled commands from the optional section.
To fix ...
-
One way, as it is just a .xml file, open it in notepad. This may not be the most convenient way, but you can see the field values at least.
-
Strange... maybe some .NET permissions problems that prevent you from executing scripts on the production machine? It's a wild guess, really. Normally you should get an exception if it doesn't like you.
Since you are doing a shell exec, try to do a start | run on your production machine and paste the command there - see what happens.
-
Yes, the default save functionality of the application is often good enough.
-
That helps.
It's not even running the script file on the production box.
I change the start of the jscript.js to this:
WScript.Echo("Start");
if(WScript.Arguments.count()==1)
{
var param1 = WScript.Arguments.Item(0);
}
...
and I never get the start message box (I do on my local machine).
If I put this string ...