>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).

The concept of user interface is similar to the Web. Basically, when I started to build Web applications, I had to think that way as well. So, what you see here in lists, is pretty much what I would have from a desktop application, which is by presenting the users subsets of data at a time. So, everything is disconnected, within a stateless environement, so is the Web.