-
Ahh - that would be a nice feature, wouldn't it. I've occasionally wanted something like that.
Unfortunately, InfoPath has no way of knowing whether a field is really not being used. It could be used in a view (that would be easy to figure out), or in code (much harder) or in rules, or conditional formatting, or filters, or possibly even a ...
-
Hi Dean -- you still posting in the newbie section?? :o)
Sorry - for this type of formatting, there is no easy way to ''copy/paste'' from one control to multiple others.
See my Format Paitner article for a few more details.
-
In IP07 (C#) you would use:
ViewInfos.SwitchView(''View Name''); // normal view switch
e.SetDefaultView(''View Name''); // set the default view during the Loading event
You might be tempted to do the following, but it's not what you might think:
ViewInfos.Initial = ViewInfos[''View Name'']; // Set the default initial view in the XML PI to be ...
-
Sorry I don't have any code snippets to go along with this, but in general, it's a basic matter of getting a value (from the loaded DOM) and setting that value (to the main DOM).
It sounds as if both schemas are identical. If so, this should make things much easier.
You need to walk through the hierarchy of your loaded DOM, getting each node's ...
-
Glad to help. Keep up the good work. Little-by-little, we all become experts!
-
There is no tree view control built in to InfoPath and I don't know of any ActiveX control that successfully gives you a tree view in InfoPath.
You can design your own custom tree view if you are a confident InfoPath developer. If you need some professional assistance, contact Qdabra Software for a quote.
-
Loading the file during OnLoad is certainly a valid option, only you need to write code to copy the values from the file you loaded to your DOM. But you must also be aware of any changes to the file and handle those yourself (i.e. rows added/removed, etc).
-
Do the envelope values get cleared upon send (I have never tried this so I don't know). If they do get cleared, then you best bet is to get them BEFORE sending. If not, then you should still be able to get the value.
-
I can't and don't speak for Microsoft, but I have worked for them in the past.
I can, however, say that do to IP issues and the need to gaurantee original sources of both the ideas, code, etc., in order to prevent legal issues, Microsoft and other large corporations tend to avoid such practices and develop in-house as necessary.
-
Take a look at your OnAfterChange event handler... it sounds like you are getting yourself into an 'endless loop'. This would occur when your handler sets a value which ultimately causes your handler to get called again--thus the loop and the error message you are seeing.