InfoPath Dev

InfoPath forms cannot access files on the local file system unless their trust level is set to Full Trust.  That is most likely the issue here.

It would help if you'd show us what your code actually looks like.

It sounds like you've tried what you need to do, but maybe something went wrong along the way.  The manual fix is to open the XML forms, and modify the href value to contain the correct new path to the template.  After doing this, does the error still show with the old template path when you open it in InfoPath?  If you re-open ...

The Modify PI tool exists because as far as we know, there isn't any other simple way to do this.  It's probably your best bet.  The alternatives are to modify all of the XMLs by hand or write your own utility to modify all of them, but time is money, and this tool will definitely save you a lot of time compared to either of ...

Sounds like you've probably just missed a small detail somewhere - maybe misspelling a node name, or leaving out a my:.  Works perfectly fine in this form. I assume you also want to prevent duplicates within the same row, and I've added logic to do that too.

Since I'm guessing Employee is a non-numeric value, you need quotation marks around its value: concat("Delete /xpath=/my:myFields/my:Labor/my:MasterLaborCall/my:MasterLaborRepeating[../my:MasterLaborPerson='", Employee, "']") That's SINGLE QUOTE  DOUBLE QUOTE before the first comma, and DOUBLE QUOTE ...

To the best of my knowledge, this functionality isn't available outside of VS 2005.  However, with one license for (each of) your dev machine(s), you can use IP 2010 with VSTA to create IP 2003-compatible forms.

One clear issue is that you are using AppendChild to try to set nodes' values when you should be using SetValue().  I'm not sure what the issue you're describing is though.  What do you mean, specifically, when you say "the current row?"

Have you tried signing the form with a certificate and then publishing to the share it with InfoPath's built-in publishing features?  There is a chance that that might work.

I don't believe Microsoft has provided any APIs for manipulating XSNs.  An XSN is essentially a CAB file, and to modify one, you would extract it, make your modifications, and then reassemble it into a CAB and save it with an XSN extension.  CabLib is one such library for doing this.