-
Where is the thread? Can you include a link for the thread as well...thanks
-
It was coming in at the variable. But I figured it out. I had some typos in my XDocument line.
Thanks for the help.
-
Okay, I tried both suggestions and there is no difference. IFS still sends the version updated at the farm level to the browser, and the version that was previously loaded to the Form Templates list to the InfoPath client. Strange.
-
Check several things:
1. The data connection is hooked up correctly and actually returns values.
2. The data connection is set to query on load.
3. The drop-down list box is properly connected to the data connection.
Unfortunately, these connections occur before the OnLoad event. So there's no debugging them that I'm aware of.
-
Hi Lou, you only need post your question once. People will see it. I've responded to this in your other posting:
http://www.infopathdev.com/forums/topic.asp?TOPIC_ID=4626
-
Please read the following thread. Might be best to start bottom-up rather than top-down. Then download the file I posted there as a sample.
-
If you are using InfoPath 2007 there is built-in date math for such things. If you are using InfoPath 2003, you need to write code.
-
Since you are loading from a browser, I would recommend clearing out the browser cache. You can also clear out the InfoPath form template cache, by launching IP and removing the forms from the Fill Out A Form dialog box.
Beyond that, this is outside my scope... someone else will need to jump in to assist.
-
Greg, Thanks (again) for your reply. I tried your experiment and it indeed shows that when using an InfoPath developed data source, the ''Customize Commands...'' button is NOT disabled, but when using a Web Service as the data source it IS disabled.
I don't know why this is, but I discovered a work-around to prevent users from removing rows from ...
-
Rules have an open form template action--but since you want to open an existing form instead of starting a new one, you will need code for your button. The code is as follows (please convert from JScript if required):
var spFormXDocument = Application.XDocuments.Open(''http://sharepointsite/formname.xml'');