You mean like a System DSN, User DSN, File DSN? If I just had to create a DSN, I always create a User DSN. In Win9x, a User DSN is available to all users. But in WinNT/2k, a User only has access to their own DSNs. In general, I do not use DSNs unless there is no other option. I use a connect string instead. I will create a local DBC, create a connection with the ID and password info and use that. I have also used a shared DBC where I local a shared table, use DBSetProp to set the coneection string with the User's ID and Password, open a dummy remote view in a Session object, use DBSetProp again to remove the UserID and password from the connection string, then unlock the table. This way I do not have conflicts with more than 1 user trying to connect at exaclty the same time.

>Well, I'll give it a try this weekend. As for the best ODBC DSN type would you be so kind as to tell me from your experience???
>
>TIA
>
>Luis
>
>
>>No performance problem at all. This is really not much different than what VFP does for you when using Remote Views.
>>
>>>Interesting, but doesn't it adds a lot of overhead? I mean doesn't it make your app slower?