Mike,
How difficult would it be to not use a CONNECTION object and specify a CONNSTRING when you use the views. That way you could store the encrypted password in your file, use it when you access the data and it shouldn't get written someplace the users could find.

HTH.

>We have an application that needs to connect to an ODBC datasource using a DBC connection which is shared by DBC remote views. We don't want to store the ODBC password in the DBC as this would allow users with read only access to the DBC to see the password.
>
>We have been holding an encrypted version of the password in a file and the when the application connects to the database we modify the DBC connection to put in the password, make the connection and then modify the DBC connection again to blank out the password.
>
>This approach has 2 problems:-
>
>1. It creates deleted records in the dbc which lead to file bloat.
>2. Some users have discovered they can open the DBC as a text file and see the deleted records and therefore the password!
>
>Does anyone have a better means of making a remote connection but keeping the password secure?
>
>TIA