>>If I was still working full time in vfp, sheling out for such fixes might make sense. But unless a new header type for .dbf local munching is introduced, which offers > 2GB files I think 64bit will not be a game changer for giving more speed via less disk usage. Biggest wory is that those new versions did not pass testing runs similar to vfp when new versions were introduced.
>
>2 GB limit doesn't matter so much. .DBF files already like to be flu in a few wind so best thing is move to SQL Server side.

I totally agree for applications: since MS messed up SMB and oplocks, all user/customer written data should NOT be targeting .dbf.
But ***I*** often had to do some basic data mining/grouping tasks: doing these in vfp on a WS is for me sometimes nicer than runing them in a SQL backend.
And there that barrier sometimes has to be coded around with the data sets falling towards me ;-)