Hi Brenda,

We had a similar situation and converted all of our data access to go through views. When analyzing our code, we found that we were dealing with small sets of data in many cases, so the views query only the data we need. In most cases, we were able to continue using existing code (for processing, etc.) with only a few tweaks. There were sacrifices as well, such as the ability to navigate freely through a table on a form. When using views, you don't want to pull in an entire table (unless it is small) or you'll see poor performance, so we had to adjust all of our forms to accomodate this. There is no easy way to get from DBFs to SQL Server, but you may be able to continue using some of your existing code. One of the commercial frameworks may come in handy when dealing with views, but will involve extra work to retrofit your app to the framework.

>We have a medium sized application that was a Fox 2.x converted to VFP, now on verion 6. We are considering consolidating the 40 remote sites into a single central site that would be accessed with Citrix.
>
>My immediate thought is my manager's desire to replace the VFP free tables with SQL Server. Because we are an old Fox application we have many BROWSE windows, GO TOP, SKIP, SCAN, SEEK, SCATTER, GATHER, embedded in the code. We do not go to a central routine for any table handling. How much of this would have to change?? Are all the Fox table handling commands not recognized in SQL Server? Rarly do we use an SQL statement, except for creating cursors used in the reporting. In the forms we use the old Fox commands to populate the forms and update the tables.
>
>Any thoughts are appreciated.
>
>Brenda