Thanks Mike,

Can you expand on this?

>VFP only brings the data across the wire, if it does not have the correct indexes, if you are using LOCATE / SQL. If the app is written that way, then you will be better off looking to add indexes to the tables to support the FOR and WHERE clauses.

if I'm on a checkout laptop connection to the laptop with the data and I do a "use mytable" doesn't it bring all the records over the wire?

Thanks.



>>Hello guys,
>>
>>I inherited a POS application that is having issues with speed. Basically there's one laptop who is the "server", it has all the data, and the other laptops are the "checkouts" which connect to the server via a wireless network and access the data, just the server and usually 1-3 checkouts. Of course one problem is that foxpro is bringing all the data over the wireless network and as more checkout laptops are added to the network it begins to crawl (even though the tables are not that big), actually adding just one checkout it crawls. The code is a combination of everything since a few programmers have had their crack at it.
>>
>>It would be nice to rewrite the app but that's not in the cards right now, just coding for new requirements, so my question would be what suggestions you guys have to try to make the checkouts faster? (code strategies/hardware changes/etc)
>>
>>Thank you.
>
>VFP only brings the data across the wire, if it does not have the correct indexes, if you are using LOCATE / SQL. If the app is written that way, then you will be better off looking to add indexes to the tables to support the FOR and WHERE clauses.
>
>SEEK uses indexes differently, and you may be able to really speed it up, but that can take some re-writing.