-
The key to remember is that each data source has its own set of namespaces. You need to account for that when you deal with a new data source. Never assume anything about the namespaces of a new data source -- its a quick way to get into trouble.
Greg Collins [InfoPath MVP]
-
Sounds like a job for Microsoft Virtual PC:http://www.microsoft.com/windows/virtualpc/default.mspx
Greg Collins [InfoPath MVP]
-
Hi Tom, the reason I chose JScript is the same as the reason you are choosing VBScript -- because that's what I'm familiar with. I've had minimal VBScript experience, so creating VBScript forms is not a high-priority for me.
It would be my preference to provide all Examples in all languages just for the reason you brought up. But due to time and ...
-
Lee,
I'm glad I was able to help. Your form was very complex and I had to create a simplified model in order to figure out what to do. I really wasn't sure if you'd be able to accomplish your goal using the designer. I'm happy you were able to get it fixed!
Yes, the XSL current() function is extremely helpful in many areas. I plan on devoting ...
-
I got the .xml file and have evaluated the template.
First of all, using a master/detail in a print view makes no sense. That is an interactive control. And since you had only the master table and no detail section, it made even less sense. You should have only been using repeating sections for this.
Secondly, because of the structure of your ...
-
It sounds like your main data source is based off of the Web service. If this is the case then yes, your fields will continue to be populated as before.
Greg Collins [InfoPath MVP]
-
The WS adapter in InfoPath is meant for basic WS calls. If you want more functionality, you will need to write your own SOAP. There should be plenty of info already available on the public nrewsgroups on SOAP.
Greg Collins [InfoPath MVP]
-
Great! Thanx for posting your solution!
Greg Collins [InfoPath MVP]
-
It really depends on your backend storage solution. If you are storing each ''record'' as a separate form, then you might as well just find a convenient way for the user to load the appropraite form. If all you records are stored in a single .xml file or as a database, it would likely make more sense to have a multi view single form.
But these ...
-
You are fine. Don't worry about the ''my'' namespace. It is used for forms created from the ground up in InfoPath.
Greg Collins [InfoPath MVP]