You're welcome, Tiong.

Noted and thanks ivan

Yep, if there is already an ApplicationKey in the connection data store, the call to ConnectionManager.SetConnections() won't show you the connection Wizard anymore. Also, you can even share the ApplicationKey between different applications if they all require the same connection information. So, basically, you don't need to change the ApplicationKey every time you generate a new EXE, unless you need to for some special reason.

Ivan,

Yes i did change the ConnectionManager.ApplicationKey. Is that you mean that even connection is different set at client's PC but same application key then system won't prompt the connection wizard form anymore?

Edhy Rijo,

I will try up your method.


Thanks

Connection information is saved in the Common Application Data folder of each workstation, make sure the End User have enough rights to write to that folder.  Sometimes you may need to run your application the first time "as Administrator" to allow the connection information to be saved properly so it will be read the next time your application runs.

Edhy Rijo

Hi Tiong.

Are you changing the ConnectionManager.ApplicationKey for each EXE you produce?

Hi all,

System always prompt me database connection wizard to set up the connection after i update/replace the EXE with the latest release.
How do i make system remember the connection and don't prompt me the database connection wizard upon i replace the latest version of EXE?


Thanks