Hi!

No easy way for this. Its depended on how related tables are used in application. For example, when you show parent in one grid and child in another - you cannot make a single view, you require to split them and change logic of the child view refreshing - child view now will be queried with parameter(s) - parent record information. This require additional code. When refreshing was not centralized by special function or procedure (remember that child table in SET RELATION is refreshed as soon as record moved in parent table), you will require to find all places where refreshing is made (where record pointer changed in parent table) and change all of them. And this is only a single form and relationship. On the other side, certain relationships are used in a single REPLACE command just to update data in both related tables using some business logic. Such things easy could be done using T-SQL commands ran n the SQL Server using SQLEXEC() function. It depends, but I can tell being 90% sure that C-S app written in old FoxPro without aware about moving to SQL Server in future require to be re-created again with another design. From my experience most such applications require even different interface. Only fact that all data transferred to client during a query from SQL Server puts a limitation to interface - you cannot allow each user to download >50K records often. In old FoxPro program you just open a table, that does not download all data so workd much more quickly. Based on this point you can imagine what changes are required. Keep in mind that SQL Server is supposed to work with large number of little queries from many users. Large queries cause a big overload of the SQL Server and thus significant slow down of C-S application for all users. Well, its also depended on the number of users that use application...

Take a look also to following link, it might be interesting for you:

http://fox.wikis.com/wc.dll?Wiki~MissionImpossible~VFP

>Hi,
>
>Tnx for the answer. That also means all forms with relations in dataenviroment must be changed.
>How do you normally solve this kind of problems? Do you create a remote view with both tables joined together.
>