LS

We now use (in dbIsam 3.3) a table that holds links to images that are in a
directory on a webserver (due to the fact that storing the images in a field
isn't fast enough over the wire with dbIsam). We'd like to store images in a
Blob field in a table that is NOT on the webserver, but on a customer's
server. In a webapp (intraweb witth kbmmw middleware components) we would
like to make a connection to that table and show the images (for example in
a grid). Is this an approach that would work fast enough (with ElevateDB) or
is this to be expected slow alltogether?

Regards, Harry

Harry,

<< We now use (in dbIsam 3.3) a table that holds links to images that are in
a directory on a webserver (due to the fact that storing the images in a
field isn't fast enough over the wire with dbIsam). We'd like to store
images in a
Blob field in a table that is NOT on the webserver, but on a customer's
server. In a webapp (intraweb witth kbmmw middleware components) we would
like to make a connection to that table and show the images (for example in
a grid). Is this an approach that would work fast enough (with ElevateDB) or
is this to be expected slow alltogether? >>

ElevateDB is much faster in this respect because it caches rows, including
BLOBs, with remote connections.  DBISAM only cached the row data and needed
to pull over the BLOB for even something as simple as getting the size.

--
Tim Young
Elevate Software
www.elevatesoft.com