>>>Hi everyone,
>>>
>>>I created a view, which is based on two tables. One table from Stats database (this is the one which is relevant for this application) and another table from JobControl database, which I used only for display purposes (I want to show customer name from customer table). My colleague suggested to use just tables instead. Well, I still want to use p-view, but I'm thinking, may be instead of adding customer table into my view, I can put seek(oJC.CustID, JobControl!Customer, CustID) into the controlSource for this textbox on the form (it's for display purpose only). What would you suggest?
>>>
>>>The form only uses one record from Stats!CustomerInfo for the customerID=oJC.CustID
>>
>>In principle the idea should work fine. Some frameworks work that way by default (often what they call "lookups").
>>
>>If the ControlSource won't accept the SEEK() or you have problems, define a custom function or method and use that instead.
>>
>>The main issue will be coordinating its refreshes with the rest of the form but that shouldn't be hard to do.
>
>Thanks, Al. So, basically you suggest to proceed with the idea I described, right?
Yep.
>Is view based on tables from separate DBCs is a bad idea in general?
I don't know - I've never done it.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up