-
Hi -- a single = sign is used to set a value. Basically, in your if statement, you are setting the value of LastName to null. Use '=='.
Do you know how to set a break point and run your code in debug mode? Are you using Visual Studio or VSTA (comes with InfoPath)?
-
Ah, okay, you are using the InfoPath 2007 Object Model.
To check for blank, you can do something like:
// Create an XPathNavigator to walk the main data source
// of the form.
XPathNavigator xnMyForm = this.CreateNavigator();
XmlNamespaceManager ns = this.NamespaceManager;
// Set the fields in the form.
//check to see if the ...
-
If you are populating the fields in code, you'll want to address this in code. Before you populate each field (Name, Address, etc) simply check to see if the field is blank first in your code. So, I'm guessing since you say an OnLoad event, you are using the IP 2003 object model, and you'd want to see if the .text for each field was ...
-
It sounds like you have it set up correctly. What is the exact error you are getting?
-
I don't know what 'tombstone' information is? If you are getting information from a secondary data source and want to keep it with the form, you need to populate main data source fields with that information. Are you currently doing that?
If so, I'd assume you have fields in your form's main data source like ...
-
In your form open rules, add a rule with the condition that the user's role is the role you've already created. Then add the action to switch views to the view you wish. Make sure that view has the button you want that allows the user to switch to the Submit view. It is pretty straight forward -- is there a particular part of the logic you ...
-
Hi --
Love your signature tag line, by the way.
The experience you are now having has been what I've usually seen for data validation. I usually have used code when I want it to behave differently. You don't mention the default for zero value in the form that is working. I'm guessing zero, but may be worth checking to see if you have ...
-
Printing prettily is not one of the things InfoPath does best. I'm a little confused by your question -- first you suggest that you want to print one of your repeating sections on each page, then three? However, this blog post from Matt Faus may help you....
-
You'll want to create user roles for this. You can add a button that will switch views and only display to users in certain roles, or you can switch views on form open if the user is in a certain role. Office Online has some great info on user roles and the order in which they are applied.
-
Look at your form in design mode. Make sure that the option buttons that don't work are all bound to the same field. You may want to remove the buttons that don't work and try adding them again.