InfoPath Dev

Greg, You said elsewhere: quote:To answer your first question... the default view *IS* taken into account during preview from the designer. And I replied: quote:Hmmmm.... So now I technically have two problems (at least on my machine) then: 1. Default View is *not* taken into account for me from design mode (as per repro steps below on brand ...

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? In a test, I create a blank form and an extra view, i.e. ''View 1'' & ''View 2''. I set ''View 2'' as the default. I save. Now, I find: * if I ''Open'' form to fill ...

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

Unfortunately I think not... That blog says pre-SP-1, managed code, changing views in code. I'm SP-1, MS Script, and the whole point is I'm not changing views in code/rules/roles, I'm just trying to get the default view defined in the design to show up firt at runtime. Also, FWIW, I've cleared the IP cache (which the blog seemed to be about), ...

Sorry, I should have posted earlier as I know you have to set the SelectionNamespaces for any & all secondary DOMs before XPath querying. That's all this is. This should probably be pointed to anyone using multi-DOMs, as I've seen questions to this effect elsewhere. I have one question. I do not use managed code or ''IXMLDOMDocument3'', I'm ...

Thanx for sharing the solution with us! Greg Collins [InfoPath MVP]

Never mind again. Figured it out. After oh 4 hours of researching. It turns out that I should have been using IXMLDOMDocument3. No documentation that I've read so far says I should use the new interface. Anyway doing the following will work: [InfoPathEventHandler(MatchPath=''/my:myFields/my:field1'', ...