-
In order for the user to open the XML file in InfoPath, they need to have access to the XSN related to it. This means either (1) Putting the XSN in a public place, such as the Internet, or (2) Using a URN-based solution (i.e. publish the form to a list of e-mail recipients, or use an installable template).
-
To the best of my knowledge, there isn't.
-
If you think you'll be making a lot of changes to the form down the road, a repeating section that cannot have items added or removed might be a good solution. This would allow you to set up the controls just once, and have them work exactly the same way for each workday. In Tools->Default Values... you will see a dialog that ...
-
If you'll read Qazi Anis' post more carefully, you'll see that he's suggesting making two sets of conditional formatting: one for field1-field5 and one for field6.
-
It seems that even if you use that crlf trick, InfoPath changes the line breaks from CRLF to just LF at some point. Not sure why this is happening, but you can do the following to get around this. This is C# but it sounds like you can figure out the VB equivalent:string value = ...
-
I'm not really sure what you're saying, but I assure you this is entirely possible and something that I do all the time. Please see the attached XSN.
-
I've encountered this situation before, and it seems that this is indeed a limitation of browser-based forms. I'd recommend giving qRules a try. It will also save you the trouble of cracking open your XSN to hack the manifest.
-
You should be able to use current()/my:ID (or whatever the field is called) to reference the ID in the same row as the expression box.
-
It sounds like you should be using an Expression Box to show the description instead of a Text Box. This will save you from adding a field to your main data source to hold the value. Since your data is repeating, you'll also need to use the current() function when setting up your expression, but it sounds like you may have figured that out ...
-
Creating and using a WinForm in an InfoPath project is a piece of cake. You don't need a separate assembly. Just right-click the project name in the Project Explorer of MSTA, select Add->New Item..., and then Windows Form. Drag in controls, expose their values with some properties, and add OK and Cancel buttons that ...