-
You have to reference an interop assembly that can talk to that ActiveXObject...
In Visual Studio, click Add Reference and see if the control you want to use is already listed in either the .NET or COM tabs. If it's not you need to use the AxImp.exe that is part of the .NET SDK to generate the interop assembly.
Once you have the reference ...
-
Well, loadXml takes an xml string of a form "<tag><anotherTag/>...</tag>", not a path to a file. So first you need to load the text from file using FSO and then you can load it into an xml document via loadXml
-
Since you have probably read all the UDC-related blogs on the InfoPath Team Blog (http://blogs.msdn.com/infopath/search.aspx?q=udc&p=1) I will not go into much detail other than mentioning that the biggest reason why you need to convert to UDC is because otherwise you will not get a chance of properly authenticating (maybe things will still ...
-
So you can finally get your XML file into a DOM, right? Great!
If you share out our XML file and the code you use to read it maybe I could see why you're failing to read the data.
-
Very cool, I am glad you were able to find a workaround. I will keep you posted if I find out more about this!
-
Well, if you can get it as text first then you can get it as XML by doing LoadXml(). Let me know if the load-as-text trick works!
-
Hello Michael,
Thank you for sending me your solution, I have looked at it and the problem is indeed a schema issue: your schema is too complex for InfoPath Forms Server to handle correctly.
I have created a simple repro of the problem by simply creating a new empty solution from your schema, dragging a few controls into the view and adding ...
-
Very interesting! My guess is that your schemas is what really causes the problem - although InfoPath has no problems with them, InfoPath Forms Server fails to process those schemas and therefore it fails whenever you start using xpaths on those. I would not be surprised if you also had problems with Rules and Calculations or Expression Boxes (let ...
-
If you cannot share out the entire solution try to see if you can simplify it while still getting the error - remove business logic, extra controls and aux-doms...
Or other approach is to create a very simple solution, add the conditional formatting that you have there and see if it crashes the Forms Server.
-
Hello Michael,
From looking at the log, it looks like you are hitting a bug in InfoPath Forms Server. It is mostly caused by Forms Server choking on one of the xpaths generated by your conditional formatting. I would be extremely curious to see the solution you have, would it be possible to share it out?
A few questions:
- did you design ...