>>>Is view based on tables from separate DBCs is a bad idea in general?
>>
>>I don't know - I've never done it.
>
>Hi,
>a view or (a SELECT SQL) with more than one database works fine as long as you use complete naming for the table in FROM - JOIN clauses (DBCname!TableName).
>
>SENDUPDATES will work as well.
>The rules for view's properties are the same as if you have one DBC. ALLWAYS use "DBCname!TableName" for fieldnames and tables.
>
>Finaly SET RELATION TO ,LOCATE, SEEK, SEEK() will all lead to the same result.
>But this is the same as with one DBC.
>For me, there is no general idea - it's by everybodys mind to use the one or the other way.
>
>You need to find out what is fast - and what needs a minimum code to enter. ::)
>
>Lutz

Thanks a lot, Lutz. For this particular application I realized, that I don't need to include the second table in a view anyway.

Thanks again.