>>>>also, are you saying that using SQL Server would be faster on
>>>>a WAN? :)
>>>
>>>Yes. Because all of the query processing happens at the server, SQL Server only needs to send the results back over the wire. When you do a query with just VFP, VFP needs to pull at least part of the index over the wire to find the right records to return. It then has to bring those records over the wire. Generally, VFP performs best with a powerful workstation and a fast network. SQL Server's performance depends mostly on how powerful the server is (though both can be slow if your queries return a lot of data over a slow network).
>>---
>>thanks again Josh - I must use the VFP tables for my app. On the WAN, the lines are being changed from 56K to T1 lines. Do you think that will take care of my
>>problem with data retreival, since my apps runs great on a local area network?
>>:)
>
>It'll help, but not as much as you'd hope. T1 data rates are around 1/8th the rate of 10Mbps Ethernet; the advantage of course is that Ethernet is very distance limited (a big Ethernet installation is measured in hundreds of meters, not miles). To get equivalent data rates to Ethernet, you're talking about going to a relatively fat pipe - perhaps T2C or T3 bandwidth, which frankly costs a fortune.
---
hi ed - ok - is my answer to use a SQL server? Is using VFP data files
on a WAN a bit to much to ask from MS?