InfoPath Dev

You can write code to automate Excel, Or, import the XML from within Excel, Or, make the secondary data part of your main DOM! Excel has some good XML support in 2003. You can specify a binding and load the xml saved by InfoPath into Excel separately (from Excel). There are some limitations - for example, Excel won't deal with rich text nodes nor ...

quote:Originally posted by jonbrave OK, I'm starting to look into this. Can I *please* have an answer first off to a very simple question: is ''Default View'' taken into account when previewing from *design* mode? As you now know, it isn't. The designer opens whichever view you are on when you preview.

Hi Code Wizard, I think Greg's option might still work if you use a reference to name. Another alternative would be to create the xsd schema outside of InfoPath and load it into InfoPath. Using references ought to work here too. Good luck!

Note: this translate is useful if you are doing filtering and you want to do a case insensitive filter on a text value.

Not sure I understand your scenario. You'll first want to add a separate datepicker to your form and then write some code to change the queryadapter command to specify the date window. The SDK has a good example of Data Interop which shows how to programmatically set the command property. good luck!

Hi JB, Interesting post! There was a bug in InfoPath that I discovered that was exactly like what you describe here and that's why Greg suggested reading the blog entry. It's possible that you have discovered another bug in InfoPath. You should post repro instructions so that people from MS can take a look. Cheers! Patrick

Hi Tom, You can mark the form protected which will prevent the edit in designer button from showing on the tool bar. Go to Tools-Form Options-General and click ''Enable Protection''. In addition, if you don't give them read-write access to the file-share (or web page) where you publish the xsn, they can still create forms but won't be able to get ...

You can use a simple filter for the first name and middle name dropdowns to set their values to be equal to the sibling nodes of the last name element when the last name element changes. Dbl click on the 2nd and 3rd dropdowns. You will have them bound to a secondary data source. Clicking on the binding button to the left of the datasource radio ...

Hi Steve, Welcome to our forum! When I was at Microsoft, my team worked on Export to Excel back in V1 days and it hasn't changed significantly in SP1. I should be able to answer your question or point you to the right resource. Exporting to Excel only supports using one table and all non-repeating leaf nodes, or just all non-repeating leaf ...