[AccessD] AXP and Error 3310

No, I've checked that.  It takes over 80,000 imports to make the db get
up to 1.5 Gb without any compact on close (tested it).  We do a compact
on close to compact the file when it is shutdown and restarted.  The
restart app keeps checking to make sure the window has completely closed
before it tries to restart the application in order to handle the
compact on close delay.  In the test situation, we're overwriting the
same data repeatedly to the same folder, and the temp files are being
deleted after import, so the space should be available for reuse.  I
have seen no indication that memory use is spiking or that is is even
approaching the limits.  The free space on the drive doesn't appear to
be suffering, nor does the available resouces for other apps.  Between
restarts, the database bloats up to 50MB to 150MB, depending on how many
zip files we use in the test.

Charlotte Foust


-----Original Message-----
From: Stuart McLachlan [mailto:stuart at lexacorp.com.pg] 
Sent: Monday, August 09, 2004 3:15 PM
To: Access Developers discussion and problemsolving
Subject: RE: [AccessD] AXP and Error 3310


On 9 Aug 2004 at 9:39, Charlotte Foust wrote:

> I may have misled you.  The same file is being unzipped to another 
> folder, the multiple text files imported from that folder into 
> temporary tables, and the temp folder cleared.  Then the data is moved

> from the temporary tables to the main tables.  Then a timer starts and

> the next check for files to import doesn't happen until the timer 
> interval has elapsed.
> 

If you are filling and clearing temporary tables hundreds of times, are
you 
sure it's not a case of the database bloating  - either until it hits
the 
2GB barrier or the workstation runs out of space on the working drive? 
-- 
Stuart


-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com