>>>>>>>>Thank you. I may break the query just to be sure that the user has access to the second database. Also, I don't like to use the DB name in the query (it would be hard-coding it). I prefer to use a handle.
>>>>>>>
>>>>>>>Nope, you can not use handles.
>>>>>>>You must use DataBaseName :-)
>>>>>>
>>>>>>I wonder if I can use a pseudo name for the DB so that I don't have to hard-code it in my query.
>>>>>
>>>>>Nope, you can't.
>>>>>But you can create Synonyms in you database to create instance of table from other database and then use that synonym like table.
>>>>
>>>>Could you, please, give me an example on how to create a synonym?
>>>

>>>CREATE SYNONYM schemaname.SynonymName FOR DataBaseName.Schema.TableName
>>>

>>>Than you can use it:
>>>

>>>SELECT * FROM YourTable
>>>INNER JOIN schemaname.SynonymName ON ...
>>>

>>
>>Thank you. Is CREATE SYNONYM a VFP command or SQL Server command? ( I cannot find it in VFP help)
>
>SQL Server one.

Actually I found that I can create a variable for the 2nd DB and set the name of the DB (on log in) to the variable. This way, the SQL Select uses the variable and the code is not hard-coded to the name of the DB. So far it works.
Thank you all.