You searched for the word(s): 2
-
-
The sample form is included as part of the installation. If you did not install the sample forms, you still can by modifying your install of InfoPath/Office.
-
You can switch views in the Loading event, however it works differently. Rather that calling the method to switch views, you set the property for the view to identify it as the default view.
-
You are close. It's still not working because you only made half the change. Note carefully the difference in the XPaths:
BAD: e.Site.selectSingleNode("/my:myFields/my:Dealer_Info/my:Dealer_Name").text = elements[0];
GOOD: e.Site.selectSingleNode("../my:Dealer_Name").text = elements[0];
You are using ABSOLUTE XPaths ...
-
On the Loading event of a form, we are getting data from a SQL database and popping it in the form...
If data that the form is expecting, doesn't exist, the form throws an error (which we are gracefully catching.)
What I would like to accomplish is to catch this error, and switch views to a "You are not authorized" sort of ...
-
What larko_s was really trying to say (I talked to him about it offline) was that he wants to modify the schema to allow attributes to be added.
(forgive me for putting words into your mouth)
-
I tried to get to your document through its parent Window object. I accessed some read-only properties just to see if I could get in, but Ireceived the following errors:
?this.Application.Windows[0].XDocument.DOM
'((Microsoft.Office.Interop.InfoPath.Window2)(this.Application.Windows[0])).XDocument' threw an exception of ...
-
I have a bunch of forms that I need to update in design mode to include 2 attributes to each element/control (whatever is the correct term). I have built an add-in that shows the menu item under Tools, but on click, it opens a new, empty InfoPath app window.
Here is the code I tried:private void ...
-
Nevermind. I was just trying to switch view in the catch section, which you can't do...
-
When loading a form I get the fairly generic "There has been an error proccessing your form" message.
I know WHY this is happening, and it could potnetially happen in production.
My question is, is there a way to catch this error and redirect the user to a slightly more user friendly (me created) error page?
Trying ...