InfoPath Dev

It is not the number of calculations, it is a loop that causes the problem. For example, suppose you have two fields, field1 and field2. If you say "field1 = field2 + 1" and "field2 = field1 + 1", you've got it. It is just two calculations, but they call each other infinitely. You start with field1 being empty, field2 ...

This is typically indicative of a bug in your calculations (usually a loop) such as "when field A changes, compute field B" and "when field B changes, compute A". InfoPath has a limit of about 20 calculations after which this message appears. It cannot be supressed but if you fix the error then it will just go away.

I do not recall seeing a VS crash recently but here are a few things you can try: 1. You say you are working on a vista machine because you "need to use the MOSS object model". Is your VS fully patched? I think you need to install SP1 and maybe another update before VS will run well on Vista. Also, if the only thing you need ...

Yes, I think I know what your problem might be: you are using absolute xpath instead of a relative one. An absolute xpath starts from the root node (typically it is prefixed with /) while the relative one starts from e.Site. Just think of what e.Site represents and compute the closest possible path from there. I hope this helps...

One idea would be to set your submit to "perform custom action using Code". It's a bit more work and if your current template has no code deployment will become that much harder. However when you submit using code you can cancel submit based on some conditions, namely the ones you have.

So you are correct about the T meaning time, YYYY-MM-DDThh:mm:ss is a standard XML format for date-time. The full URI as you know it gets assigned to the form template when you design it and it becomes the template's identity. If you design a new form in InfoPath Designer and click File|Properties, you will see this value there: it will ...

InfoPath has a feature called "merge forms" and it is much better supported in InfoPath 2007. I have not played with it in a very long while so I cannot give you a specific example, but basically you can merge any number of documents into one (merging with code allows you to do it even when schemas do not match, that is, when the target ...