-
Hi Swetha,
It's some work, but you can write code to do this.
Good luck!
-
Hi Brett,
Could be any number of things from cross domain security (is the new server in the same domain as the user opening the form? does making the form full trust solve the issue?) to host header issues resulting from the SP2 reinstall.
You've been using ADWS for several years. We have a more recent version if you're interested ...
-
You are barking up the wrong tree. Why not have two buttons that conditionally show based on who opens the form? Then, you can set a value in the form and save it and next time opened you can use conditional formatting and/or On Load rules to change what displays.
-
Use buttons in tables with conditional formatting for the rows (to hide them).
-
Hi JTownson and welcome,
Congratulations! You have found a bug in InfoPath 2003 when designed with InfoPath 2007. Try creating a form template in InfoPath 2003 designer only. Good luck!
-
To filter on the current row you'll probably have to manually modify your XSF. It is possible to do this since InfoPath supports xpath and xpath supports current row functionality. You might want to search for Current() or XSF. Greg blogged on the former several years and Jimmy has blogged on the latter more recently. Sorry I can't be more ...
-
Have you tried removing the pattern and adding logic to SQL to auto-increment the primary key?
-
Hi Iri,
I don't know much about SharePoint surveys. XML documents can be submitted to lists but you'll have to write code or use Qdabra's qRules.
Sorry I can't be of much help!
-
-
Hi Gary,
Qdabra's free Hide-Show XTP uses secondary data sources to set data. Check it out: http://www.infopathdev.com/blogs/mel_balsamo/archive/2009/01/14/hide-show-section-template-part.aspx