-
Since there is no event object, and the function returns void, whenever you want to stop processing the button click, just do a "return;".
-
Great! Glad to have helped!
-
Sadly, as stated before, InfoPath is very weak in the printing realm. However, take a look at this Blog article and see if it helps. If not, you might have the (potentially) unpleasant experience of going back to the customer and explaining the limitations and working out an acceptable ...
-
Awesome! Glad to hear you got it working!
-
Actually, I will tell you to use rules -- but not like you are thinking.
Rules run before code does. Therefore, you can have a field (can be in a secondary data source -- .xml file, whatever), that is used to identify which button was pressed. The first rule on each button sets a value on this field. Then when you enter the FormEvents_Submit() ...
-
Interesting. Thanks for sharing this information.
-
You will need to either cast it or write a small conversion function which returns a true boolean value. The problem is that if you are not in control of the form, then you could be getting anything back from a check box.... red/blue, yes/no, up/down, 1/0, light/dark, whatever!
If you are specifically in control of the form, and your not going to ...
-
Sorry, there's nothing in InfoPath 2003 that will let you do this.
-
The first thing that could be an issue: the use of "../" in your schemaLocation attribute. Try grouping all the required schemas into the same folder and eliminating the parent folder references ("../").
The second (probably not an issue, but you never know), most namespace definitions are a URI, such as ...
-
A custom toolbar button does not use the same function syntax as a form button does.
I haven't done these for a while, but if I recall correctly, you just need to create a public function of the same name as the toolbar button name, no parameters:
public void btnTest()
{
...
}