I have a project that has local DBISAM tables but is also connected to a
server via a socket layer.  It's NOT using client/server DBISAM, it's making
RPC calls to the server; custom socket layer.

My question...

How suitable is a "memory" DBISAM table, with SaveToStream at the server and
LoadFromStream at the Client, as a generic method for passing dataset
information between over the socket layer?

Thanks,

Jerry

Jerry,

<< I have a project that has local DBISAM tables but is also connected to a
server via a socket layer.  It's NOT using client/server DBISAM, it's making
RPC calls to the server; custom socket layer.

My question...

How suitable is a "memory" DBISAM table, with SaveToStream at the server
and LoadFromStream at the Client, as a generic method for passing dataset
information between over the socket layer? >>

It's perfectly suitable for such a task, and it's what is used with DBISAM
C/S for streaming datasets back and forth.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Sounds Great!

I've done some trials, works fine, but I can't figure out how to enable the
field compression for when I SaveToStream.

I've tried setting the FieldDef.Compression level before assigning data,
(get an error), and after assigning data, but before saving to stream and no
effect.

The memory table "stand-alone" and is not part of any database/session/etc.

Shouldn't I be able to at least get extra space character data (ftString
type) to filter out on the SaveToStream?

Obviously, I'm missing something, but can't find it.

Thanks,

Jerry

Jerry,

<< Sounds Great!

I've done some trials, works fine, but I can't figure out how to enable the
field compression for when I SaveToStream. >>

You can't - the stream format is fixed.  If you want to compress the stream
in its entirety, however, you can do so using external methods like the ZLib
compression library in Delphi.

--
Tim Young
Elevate Software
www.elevatesoft.com