-
The problem in this situation is that the XSN being used in each case really looks different to InfoPath. One is on http and one is on https. Given your environment, the only way to get around this would be to write server code to do the PI fixup translation on the fly when the user requests the XML file.
The primary workaround is for all ...
-
The likely issue is that the calcs are happening quickly but the view is updating slowly. These kinds of situations are hard to debug without seeing the solution.
400 rows in an InfoPath form is at the far end of the spectrum for InfoPath's capability. I hate to have to say this given your high praise of InfoPath, but Excel is better suited to ...
-
One other thing to watch closely is if you have any blank cells in the row InfoPath will make the row taller. You should at least have a blank space in every cell and the font size of that space as 4 (manually type in the number). This will ensure no extra height is added.
-
This type of solution is possible with InfoPath but would require custom code in the InfoPath form.
-
The trick is tracking which numbers are used up. This would require a central location like a database to track that.
-
One thing to be careful of is that adding to Trusted sites will disable managed code from working. Try first adding to Intranet Sites and setting security level there just to be on the safer side.
-
This is the first I've heard of this type of corruption. What do you mean that the first element is repeating sporadically under unreleated groups. How does that first element show up in the other groups?
-
Are you doing this in the Designer or Editor?
-
You can use SP2 to design non-SP compatible forms, however you can't use the new features since the older clients just don't have those features. Sorry for the bad news.
-
You must manually update your data connections to point to the new domain. To do this:
1) open the template in designer
2) go to Tools::Data Connections
3) select each data connection and click modify
4) change the url from https://... tohttp://...
5) complete the wizard (you shouldn't have to change other parameters).
6) republish the solution ...