>>You'll need to change your thinking about data. You never pull over the entire table. You work with sets of data. Think of it as always using a SQL SELECT with a WHERE clause. You'll need to have some type of query form where the user can enter their criteria and pull over only the records they need.
>
>So, if I'm using SPT it's ok to select some chunk of data into a VFP cursor and use it bound to my controls?
>
>Fernando

That is correct. You are not technically using DBFs (tables) as you are only binding to VFP cursors in memory. You fill the cursors with (limited) sets of data as Craig said.

Sergey Chavlytko is correct that this approach is very similar to what you do in other labnuages/other environments. VFP just makes it very easy to work with using CAs or SPT as Mark said.

I have a similar situation that works very well. And having the power of VFP, you could "masssage" the data locally very eaily behing the scenes. In one case I had to add support for disconnected notebooks on the field. So it was just a matter of keeping the local sets in DBFs in each notebook, then uploading changes to SQL Server when reconnecting. A very common scenario. VFP makes it easy.

HTH