Hi!

I had looked at DBSetProp and wondered about that. I like how you're doing it, but our users would complain a lot if they had to type one more password. Our production/test environs are on separate servers, so they have their own dbcs already. I suppose, thinking about this more, that I could just hardwire the dbcs in each location to point to the appropriate place and not deal with it programmatically at all except when in a dev environment, which is on local hard drives. Hmmm....
Thanks!

Laurisa


>Hi Laurisa;
>
>When I use remote data, my login screen has a drop down box of available DSN's (read from the registry). The user can select the DSN and then enter their user id and password.
>
>These values are then used to upate the connection properties (I use only one, but you could do more) using DBSETPROP. You need to update three properties, the Datasource, Userid and Password.
>
>Do this before you try to open any views. This allows you to connect to any datasource.
>
>The only requirement here is that each user have their own local copy of the Database container, as each user may choose to log into a different database.
>