InfoPath Dev

Oh yeah! That helps considerably. I did have some kind of XPATH /DOM thing within the For each at one point, but that wasn't working for me either... Now I just gotta figure out how to conditionally get rid of the sections (which should be much easier that I can actually get to those context values...) Thanks! quote:Originally posted by ...

I've been fighting with this for a couple of days and cannot see the forest through the trees... I have a view that contains a single repeating section. New sections should be inserted or deleted based on checkbox values on other views. When a box is checked and a section inserted, I am using VB.net to set a ''context'' attribute on the ...

quote:Originally posted by Patrick Halstead Jason is right on. When my team created the samples that shipped with InfoPath V1 many of us used XML Spy. :) Patrick Halstead [InfoPath MVP] InfoPathDev Woops. Yep. I've been using XML Spy for schema development. Guess I need to make my question more specific. What types of controls would I use ...

I know that InfoPath cannot support mixed content, but what of something like this as a row in a repeating table/section?: ((element-title | text | generated-number | style | graphic | generate-key-term-list | toc | chapter-number | position-in-chapter | section-number | division-number | subdivision-number)*) Assume for now that the content ...

Believe it or not, no. No attachments. Just hundreds of checkboxes all defaulted to ''0'' awaiting their chance to be part of the current state... Thanks for the heads up on the article for improving throughput. I'll go through and see what I can do. Thanks again.

Yes. The actual XML file was 2 MB when I tried to do conditional visibility - and that was all form workflow/state XML - not the actual information we're trying to capture. That's why I was really happy to find that I could insert the sections on an as needed basis. The XML file is much smaller now. But now I've got a lot more code to write - ...

I've been working on a monster form with 8 views and hundreds of checkboxes that control the state of a view with a repeating table. I encountered the Conditional Presence vs. Conditional Visibility issue in after the data source was complete, but while I was only midway through creating all of my views with their various sections and ...

Thanks again. I'll do the import before I start adding any further code, then.

Got another question for you guys... Which would be the better UI for implementing the code - the MSE or Visual Studio? I get that you get all the Visual Studio tools if you work from that interface, but what I don't know is if there's any downside to working there. I have many MANY checkboxes. Is one UI over the other going to help me get ...

Cool. Thanks!