55 million records is far too many to work with. You need a search mechanism to narrow down the number of records. For example, the user needs to find a record for Michele Bosetti. They can search for this in a number of ways, by customer number, by name, by city. You need to provide mechanisms to search for each of these. If the user chooses to seach by city, return all the records for that city into a grid. The user then selects the needed record.

The way I do this is to set each form to NoDataOnLoad and use a remote view with criteria like:

WHERE CustomerNo >= ?vpCustNo1 AND CustomerNo <= ?vpCustNo2 ;
             AND LastName >= vpLastName1 AND LastName <= vpLastName2 ;
             AND City >= vpCity1 AND City <= vpCity2

I then set the value of each view parameter. Using the above example, I do something like:

vpCustNo1 = 0
vpCustNo2 = 9999999999999    && Some really big number
vpLastName1 = ""
vpLastName2 = "ZZZZZZZZZZZZZZZZZZZZZZZZ"
vpCity1 = "Brescia"
vpCity2 = "Brescia"

* Now requery the view to fill the cursor

>We have an application that has reached foxpro's limits. We have tables with 55 milions records and 2 gb size. We have planned to pass to SQL Server but we have a question. Which is the correct way to access a table with 55 milions records from Visual Foxpro and SQL server ? I think that the problem is similar for a SQL table with 200.000 records. Now i put data in a grid and i can go top, go bottom without waiting time. How can change the situation whn passing to SQL server ? The users have to change their usage of application and understand that they'll never have a grid with all records, and have to filter data before see them in a grid or have to never use the "End" key to go bottom if they don't want to have a coffee break every move they make on a table. Someone can give me some explains about the changes in operation that we need to do and which is the berst method to access sql data (SQLExec, remote views, data objects).
>Thanks