InfoPath Dev

There should be no problem to do this without writing code. Quick sidenote: if your clients are using IP2003, make sure you always save your solutions in IP2003 (I know it's obvious but wanted to make sure). So, to achieve what you're trying to do, it's best to use rules. Double click on a control bound to Actual Amount, select ...

Salut,Effectivement, il y a moyen de le faire. Avec InfoPath 2003 tu es limité à le rouler dans sa propre fenêtre. L’objet s’appelle InfoPath.Application et tu le crée comme n’importe quel autre ActiveX (par exemple, dans javascript tu ferais new ActiveXObject("InfoPath.Application")). Il ...

First of all, as far as I know, you have to save solutions in IP2003 format if you want them to even open on IP2003 machines. Having said that, you can still use IP2007 features in those forms and they will work fine on an IP2007 machine. As far as what will happen on an IP2003 machine, it will all depend on the features. Your best friend is the ...

How exactly are you importing the form into VS2005? Could you please specify all the steps? I have written a blog on migration from IP2003 solutions to VS2005+IP2007, maybe it could be of some use for you even if the topic is a bit different: ...

Are you talking about the resource files you have added to your form in InfoPath? In this case, those files are available to be used by your code - they reside the in the same folder your assembly is being executed from. That means that if you have a file called "data.txt", you could read its contents in this way:string data = ...

I don't believe this is possible, and here is why: The Forms Server tries its best to do everything in the browser without sending data back to the server (aka postback). However, there are times when it has to be done. Any time it has been determined that a postback has to happen, Forms Server has to block the user from making any edits ...

Well, security is pretty tricky to get in Sharepoint... I have several questions for you: 1. You usually open an InfoPath form via a document library. When you configure the doclib, you can specify that it opens in the browser. Try that? In that case, what happens to the users who have InfoPath installed? Does the form open in the browser or in ...

Although what you are describing should work in principle (ASP.NET session persists across the farm) it remains that the ASP.NET session is a shared resource you do not necessarily control. Maybe the data size is what is causing the session failures. You should try to see if changing the size of your object changes the failure characteristics ...