>Robert,
>
>Outside of me giving the DBA my source code, showing him where to change the SQL Server user ID and password and having him compile it himself... Does anyone have any ideas??
>
>We usually use a DBF which stores all pertinent connection info (the fields are encrypted as well). Then, we provide a form interface for the client to change User ID, password, server IP etc as they wish.

How do you determine who is allowed to change the ID, password etc ?

This DBF is read by the app as it establishes a connection with the database server.
>
>Others store connection info in the client machine's registry.
>
>Hope to help.
>
>Dennis