Abdulaziz


If you want to do things to the data on the local machine you have to transfer from the server somehow. As Tim's already said the best way to do this is to use streams. It will mean a little bit more work because you'll need two sessions - one remote and one local and you can't use sql to transfer data between sessions.

Using something like kbmMemTable may help but I last used that before I bought DBISAM many years ago so can't comment.

Roy Lambert [Team Elevate]

"Tim Young [Elevate Software]" wrote:

Barry,

<< The EDB memory tables are only stored on the server if they are not
temporary. Temporary EDB memory tables are stored locally on the client
machine.  >>

<Abdulaziz is correct - with remote sessions, all tables are stored on the
server, even temporary tables.>

Tim,

I guess my memory is failing me. I thought C/S temporary tables were local. Arrghh!

Now I understand why C/S EDB temporary memory tables were so slow.  All of the data still had to be transferred from the memory table on the server over the network to the client using TCP/IP, which is very slow compared to accessing memory tables like kbmMemTable directly.

If I and Abdulaziz wanted better speed with EDB memory tables, we should have used a local EDB database which uses the client's memory, eliminates the slow TCP/IP protocol, and the network traffic.

My bad.

Barry

Tim,
Roy,

<<Why aren't you just using a local session and local in-memory tables (all
EDB) for the memory storage on the client side ?  Then you can use any
number of techniques to get the data back and forth, and you have complete
SQL capabilities.>>

This what I will do...thanks.
Regards,
Abdulaziz Jasser