>Isn't it true that when a workstation looks at data in a FoxPro table on a VFP form, that the entire table comes down to the workstation physically, perhaps as a temp file that is recognized as the table? And, isn't it true that this causes the LAN's bandwidth to be high if the tables are large?

It's all relative. Fox will try to minimize the traffic, but depending on how you look at the data, it may retrieve some blocks, many blocks or all the blocks. If there's an active index, and you, say, scan for a certain Rushmore optimizable condition, the information about which blocks are needed can be retrieved from the cdx file, so only the required blocks of the cdx file, and those of the dbf, are pulled over the wire. Which can still be a lot, if your records are scattered throughout the table and the table is large. OTOH, if you scan the whole table, the whole table will come down the wire.

So it is with any other system working through a file server, except the others are probably pulling even more, specially if they don't have compressed indexes like Fox has. Rushmore helps here a lot, but it has its limits.