The customer receiving such a program, needs their own license of PrimalForms (299$) + the source code if they shall be able to change the password of the RunAs user later by themselves and have the program still working, correct? (by re-building the project and entering the new password for the Run...

Ok. Is there any way to later change the password of the RunAs user in Active Directory, and have the program continue working? Or is it always necessary to rebuild the package and enter the new RunAs user password after changing its password in Active Directory.
mssapien2012-03-28 18:34:48

Okay. Where do I choose/how do I know which "hosting option" my build uses? I obviously want it to run in memory.Also I hope your higher encryption level will be implemented for all (not only for government customers).

I am making a Form Project Package and using 'Run As' a user which will have more rights than the actual user that is going to use the program.How secure/insecure is the password for the 'Run As' user stored?

Update: I installed PrimalForms on a Windows Server 2008 R2 x64 and rebuilt the package when logged in as the domain administrator. The build works fine on the client computer as well. Success!I have not tested whether it was the operative system (Windows Server 2008 R2 x64) or the user (domain admi...

Here are results from some testing.I have two domain users: internal, externalI have one domain administrator: administratorI have made four builds: Impersonate-Administrator.exe, RunAs-Administrator.exe, Impersonate-Internal.exe, RunAs-Internal.exeI login as external, results:Impersonate-Administra...