InfoPath Dev

Thanks for responding Hilary (I've previously spelled your name with two l's and I apologize!) I've looked at the "expression box" (calculated value). When I look at its properties, it doesn't have its own name, so I don't see how I can modify it from the code-behind (the idea is that something I do in code will ...

 Good afternoon! There are times when it would be nice to somehow put a field on the template that I could change without having to bind it to the database in an SQL-based template. An example might be a custom error field that I could change the contents of under code-behind conditions. During the design phase, every time I try to add a ...

Final note from me: In my automation routines, I forced the href in the templates to match what Windows was changing the path to on all the machines at the failing remote location. I modified all of their exacting forms based on the templates to match as well. All three users at that location are now working as anticipated. InfoPath was not the ...

Thanks for responding! Not a silly question at all! The only way I can reach the locations from here is via Teamviewer or LogMeIn. They're not part of an integrated network. There are 7 remote locations and about 50 different templates. Unless there's a way to automate the publishing, that means I'd have to manually publish 350 ...

Thanks for replying Hilary! Always nice to hear from you.  I didn't republish. I simply uncompressed the cab, edited manifest.xsf to point to the new location and used makecab to put it back together. Since then, another user seems to be having the problem. The last thing I tried was setting the href in the manifest to the exact mix ...

I saw a suggestion elsewhere to remove the publishURL clause from the manifest.xsf. I tried that and it didn't fix the problem.

I'm using InfoPath 2010... I have a user unable to get their work done as a result of this failure. I would appreciate any and all help! I have modified a published template for use at another physical location. I edited the manifest.xsf file and changed the location references and rebuilt the cab (xsn). I copied it to a LAN directory at the ...

 Good morning! The switch to office 2010 in the remote desktop environment took place last night, and as of this morning, InfoPath 2010 is printing through EasyPrint to the user's desktop as it should. This was not a fix to the 2007 print problem, but a circumvention, but we're satisfied that we can move forward again. Thanks for ...

 Thanks for responding, Hilary! It's a pleasure to meet you! We're using InfoPath 2007 in application (as opposed to web) mode. All of our other applications, even those based on MS Word 2007, are successfully sending their print via EasyPrint to the redirected printers at the user end. It's also working with a web page print on ...

 Does anyone have any help? I'm not finding anyone anywhere else, either.