Thanks for the reply. However, I don't quite understand how OpenViews will
help in my case. As of now, I'm thinking to resolve my issue is to change
the database property of a view to either the database containing the remote
view for SQL Server tables or the one containing the remote view for VFP
I'm trying to create forms which will handle both VFP data and SQL Server
data. I will have the following scenarios for a scx:
1. All the data will be from SQL Server only. For example, table1, table2,
and table3 are all SQL Server tables and they will be accessed using ODBC
2. Some data will be from SQL Server and some from VFP. For example,
table1 and table2 are SQL Server tables and table3 is VFP table and they will
be accessed using ODBC remote views. Table3 have structures
corresponding to its SQL Server counterparts in scenario #1.
I have 2 applications app1 and app2 which are almost identical in
functionalities except one is using VFP tables and the other one is using SQL
Server tables. Now, I'm taking an identical part out of both applications
and making it as a third application app3.
1. When app3 is called by app1, app3 will only use SQL Server tables.
2. When app3 is called by app2, app3 will use both SQL Server tables and VFP
tables. The VFP tables used in this case are counterparts of the ones used
in case #1.
"Craig Berntson" wrote: