What I do is at the start of the application, I use SETDBPROP() to set the password, open a dummy view (that will remain opened until the app closes) and immediatly use SETDBPROP() again to remove the password. As long as all the views are sharing their connections (including the dummy view), everything works.

This might not work if every workstation uses the same DBC (on a file server, for example). I prefer to have everything on the workstation (EXE, DBC, etc.), except for things that require to be shared.

BTW, as in everything, the adminitrator account (sa for SQLServer) should only be used for administering, not for everyday use.

>How can i protect the password store in the connection contained in DBC ?
>
>I try use....conntString..., but views can not share their connection
>
>so the transaction not good when 2 views updated togather.