Mark,

Thanks for the reply and normally I would agree with you, but Mere Mortals already accounts for the form problem. All my controls use v_ and the l or r are added through the business object class. I am leaning toward one .dbc and enhancing the business object class to handle a 3rd and possibly 4th set of views. I am glad to hear your opinion though since I greatly respect your kowledge regarding Oracle.

Kind Regards,

Mat

>I would use separate DBCs so you can name the RVs the same in all DBCs. This prevents you from having to code your form data sources for all varieties of backend DBs. Go with option 1 and use the prefixes lv_ and rv_ for your local and remote views regardless of the backend.
>
>When the backend changes all you have to do is point your APP to the appropriate DBC. Seemless and no additional coding in your forms.
>
>>Using MM, I have developed an application that utilizes both VFP (local) and SQL Server (remote) tables. Now I want to add Oracle and I am not sure what is the best way to handle the remote views. Should I:
>>
>>A. Have 2 .dbc’s where the rv’s in one are for SQL and the other for Oracle
>>B. lv’s for Local, rv’s for remote (SQL) and create ov’s for Oracle and add code to the business objects to handle a third set of views
>>C. other ideas?
>>
>>I have also had requests for DB2, so there may be a 4th set of views in the future.
>>
>>Kind Regards,
>>
>>Mat