Kerry,

> I also have a DBISAM server (the exact one that is included with DBISAM)
> that I can also run on the Windows 2003 server, pointing to the same
> DBISAM database folder mentioned above. Users can then choose to connect
> via a 'local' connection, or this C/S connection.

Eliminate the "Local" connection possibility so that uses only have the
ability to connect via C/S.  This guarantees that only 1 application (the
server engine) is accessing the data and should bypass the 2nd+ user
connection issue.

Just my 2cents added in where it probably shouldn't be.

--

---------------------------------------
 Terry Swiers
 Millennium Software, LLC
 http://www.1000years.com
 http://www.atrex.com

 Atrex Inventory Control/POS -
    Big business features without spending big business bucks!

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Tim

<<That doesn't make any difference at all, nor should it.  Running the Open
methods against tables that are already open won't do anything at all - it's
a NOP.>>

The form doesn't open tables that are already open, the thing is that you can see how much is the difference on the memory amount opening the
tables before using the stream memory and after that.

You will see that before the use of the stream (Load documents form) the open tables form makes the memory goes up by about 1 meg, but if
you run the open tables form  after the use of the stream (Load Documents form) the memory goes up by about 5 megs, so we have a difference
of 4 megs just in the example, but in my application that difference is about 700 Megs.

Saul,

<< The form doesn't open tables that are already open, the thing is that you
can see how much is the difference on the memory amount opening the tables
before using the stream memory and after that. >>

There is no difference as far as DBISAM is concerned.  It doesn't start
using more memory because of *when* the tables are opened.

<< You will see that before the use of the stream (Load documents form) the
open tables form makes the memory goes up by about 1 meg, but if you run the
open tables form  after the use of the stream (Load Documents form) the
memory goes up by about 5 megs, so we have a difference of 4 megs just in
the example, but in my application that difference is about 700 Megs. >>

I increased the number of rows in the table via a series of INSERT INTO
SELECT * FROM executions so that the total size of the BLB being transferred
via the record copies was over 200 megs.  The page file usage fluctuates
during the loading of the documents, but goes right back down to where it
started when it is done.  And when the tables are opened does not matter,
the memory consumption is the same.

I'm sorry, but until you can send me something that actually demonstrates
what you're talking about, I really can't spend any more time on this.

--
Tim Young
Elevate Software
www.elevatesoft.com