What I've done in the past is use remote views for the different databases, then create a local view that contains the two remote views joined together -- I'm even doing updates this way. I have had others tell me that this is not necessarily a good idea -- however I've yet to ever have a problem doing it & been doing it for many many years. I actually have local view that contains remote views from DB2, MySQL, Oracle, two SQL databases and 2 VFP databases all wrapped into one local view lol.



>Hi,
>
>I am working on modifying a SQL Select that pulls data from two databases.
>The first one is the default.
>The second database is specified in the variable cSecondDb. For example,
>

>cSecondDb = "SQLDbNo2"
>

>
>In the SQL select I put the variable cSecondDb as a prefix to the table that is in the second DB. Example:
>Table 1 is in the 1st DB
>Table 2 is in the 2nd DB
>

>select column1 from Table1 where column2 in (select Table2.pk_field from " + cSecondDb + "Table2" +  where 
>Table2.field3 = 'xyz'
>

>I know that the above is probably not well formed SQL Select. But my question is,
>Do I need to put the variable cSecondDb before EACH and every time the table in the second DB is used? Or just in the FROM clause?
>That is, do I need the cSecondDb before "select table2.pk_field" or by saying that I am selecting FROM cSecondDb + "table2" is enough?
>TIA