InfoPath Dev

For both Catharine and boverton: If you have an XSN it'll probably be good to upload it here so that I could take a look: http://www.infopathdev.com/files/folders/community_uploads/default.aspx  

You might be just hitting some obscure bugs or limitations of InfoPath - after all this is pretty advanced stuff which uses an undocumented feature (who would have known that eval() actually returns an xml tree?) As a matter of fact, "undocumented" sort of means Microsoft reserves the right to change it any time and we cannot blame ...

This is very strange, I have tried exactly what Catharine said and it works very well for me. Obviously it was not the exact same thing... Can you share out your solution XSN? I am not able to reproduce your problem from the information you have provided so far.

Hello Catharine, no reason why it would not work... I have created your schema as you have specified it and my eval works: xdMath:Eval(xdMath:Eval(../my:ApplicationServerGroup, 'concat(my:ApplicationServer, ";")'), "..") The way you have your schema seems right, why would you want ApplicationServer to be repeating ...

You're mentioning XmlFormViewer so I am assuming you're hosting Forms Server in your own ASPX page. While I am not aware of any official blessed way of getting notified on save there is one thing you can try. The "save" button is nothing but an Anchor tag with an onclick event. Since you can run javascript in your ASPX, try to ...

Not really, no... see this thread for some ideas, though: http://www.infopathdev.com/forums/p/7052/25747.aspx

Unfortunately you will need to re-write your code - I am not aware of any tool that will convert jscript-based InfoPath solutions to ones written in C#.

In order to develop in VS2005 with InfoPath 2003 you need the toolkit which is only available to MSDN subscribers. This thread has more info: http://www.infopathdev.com/forums/p/5661/21210.aspx

Off the top of my head I cannot think of an OM that would do it directly. However, you have a few options: - If you do not use submit, set up a bogus submit adapter and make sure the form is set to close on submit. Then call Submit() from your code. Note that the browser window will not be closed but instead a message will be displayed that the ...

Do you have any sites on the default port? I am not sure what kind of a setup you have (a farm, perhaps?) but a default standalone SharePoint installation will have a site at the default port 80. If you don't have one, consider adding a site there and see if you can publish there (typically it will be just the root path such as ...