If I needed another reason to avoid VFP tables (and I don't) this would suffice. Even though the local views are parameterized, the entire table is loaded onto every desktop each time the view is opened. The waste of resources and the giant security loophole are even more significant because many of the users run the app over a 28.8 or 56K unsecured phone line. Is this unavoidable where VFP data is concerned? Converting the data to SQL Server is out of the question since it doesn't belong to my app.

The good news is that the data is NOT being buffered a second time. Instead, it seems there is some latency in getting the local view's updates out to the other workstations. I suspect this is due to cacheing. I'll leave it to the client's IT staff to seek a compromize between network performance and accurate data.