Thanks Bob,

I am going to have to programmatically select the correct database based on the Login ID, but I don't see that as a problem.

My big concern is that there may ultimately be hundreds of these databases. Just the logging (and related maintenace) has me thinking very hard about it.

Cheers,

JimN

>>Given a VFP environment I might elect to have each companies data in a separate DATABASE, (opening) switching to the active database as required. There could be a few hundred companies serviced and multiple copies of the app. could be used.
>>
>
>Jim,
>
>FWIW: I am doing this very thing with the ap I am currently developing. Basically, on the login I have a drop down of DSN's which the user can select. Once logged in, they access that database and only that one. However, they could run another instance of the app an choose a different dsn.
>
>Or, if that wasn't enough, you could go one step better, and as someone said, create a new connection to the server for each database the person wanted to work on. I guess with your form manager you could pass the connection to each form so that it uses the correct database.
>
>>1) What are the implications on performance/response?
>>2) What are the implications moving the databases off of the network server if this (separate databases) is done?
>>3) What are the implications on database maintenance?
>>4) What are the implications on LOGGING (can it even do it, can it do them all in 1 or would there be 1 for each)?
>>5) What else might make this a bad idea?
>
>As far as all the above, I don't think having one or many databases changes it, except that you have to deal with them in your maintenance tasks, etc.
>
>>Any comments would be helpful.
>
>HTH,
>BOb