>>
>> >>>In FPD I used to use pc anywhere that refreshes the clients screen, but
>> this does not to be workable anymore in a GUI environment,
>> >>
>> >>I use Remotely Possible 32 from Avalan and am happy with it.
>> >>
>> >>chris
>> >
>> >Arnon, Luiz, Craig and Chris,
>> >
>> >Thanks.
>> >
>> >If I read you, I must conclude that my hypothesis is wrong. That C/S, by
>> sending only the request to the DBMS and receiving back only a cursor of
>> data is no cure for the problems as I explained them to you in my request
>> for explanation. You seem to imply that the way Foxpro handles that over
>> communication lines to and from a (then) file server cannot be markedly
>> amelioated by implementing C/S.
>> >
>> >Puzzling.
>> >
>> >Thanks again and regards,
>> >
>> >Marc
>>
>> Well, the answer is...it depends. How much data? And
>> particulalry...indexes, which is what will be transmitted for the
>> searching. And when the desired data is found, how much will be
>> transmitted. Do you want to see a list of all clients? Then the entire
>> client table has to be tranmitted? Are you looking for client #34582? Then
>> the index is transmitted...followed by the data. Then, when you want to
>> find client #634232, the entire index is again transmitted...again followed
>> by the data. The choice to go C/S really differs for each circumstance.
>
>Should the entire index be transmitted; or should it only be the index
>nodes to get directly to the correct record? And can't you transmit the
>table in chunks, giving the impression of an immediate response while
>the rest of it is loaded in the background?
>
>/Paul


No..the entire thing needs to get transmitted....using standard VFP. All the processing takes place on the local machine. The backend server (Novell, NT) has no way of knowing which pieces of data are perttinent.

Craig