[AccessD] AXP and Error 3310

DWUTKA at marlow.com DWUTKA at marlow.com
Thu Aug 12 09:14:16 CDT 2004


Of course it doesn't....that would make life too easy! LOL.  I love getting
error messages that are so vague they let to spin your wheels for a few days
before you accidentally trip over the solution!  

Gotta love it!

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
Foust
Sent: Wednesday, August 11, 2004 5:02 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] AXP and Error 3310


I'm still tweaking it.  I've had two apps from the start.  A few things
like the license expiring will stuff it royally, and any error that pops
up a dialog.  I'm on the heels of one, and testing to see whether I have
plugged it, but only time will tell.  Naturally, the error message
received doesn't seem to have any relationship to what is actually going
on!

Charlotte Foust


-----Original Message-----
From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com] 
Sent: Wednesday, August 11, 2004 12:22 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] AXP and Error 3310


That's pretty much what I was saying.  You have 2 apps, one to run the
process, one to cycle the first.  Is that setup still locking up?

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
Foust
Sent: Tuesday, August 10, 2004 4:58 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] AXP and Error 3310


I don't quite know what loop you mean.  When the restart app opens, it
writes a status flag to the registry.  We could have used text files or
some other means, but the registry usage is consistent with our other
apps.

The primary app is waiting to see that flag before it shuts down.  Once
it sees it, the primary app writes a flag of its own and issues a Quit.
If the restart app fails to open or doesn't write the flag, then the
primary app doesn't shut down, it resets its restart interval for an
hour later and goes about its business.

Meanwhile the restart app is waiting for the flag from the primary app.
It has already captured the hWnd of the primary app window, so it starts
checking to see if the window has finally closed.  It doesn't attempt to
restart the primary app until that window is closed.  It tries for up to
5 minutes to fail when trying to return the WindowText of that window.
If the window never closes, the restart app shuts itself down after
writing a failure status to the registry and it retains the log text
file it has been writing along the way.  That means that even if the
primary app closes but the Access window stays open for some reason, the
restart is never attempted.

Charlotte Foust


-----Original Message-----
From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com] 
Sent: Tuesday, August 10, 2004 1:12 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] AXP and Error 3310


A funny side not to my earlier post.  I had a ton of windows open on my
screen for the last few days....and about an hour ago, I started closing
things.  One of the items running, was that 'test' db I whipped up.  It
was still going.  I thought that was odd, because it couldn't have
ported that much information (into 97 .mdb). So I killed it.  Took a
look at the file size, and it was only 11 megs.  I think that it was
'reporting' that it was working, but still had the same 'lock'.  Can you
take your code of the loop, and have it run it externally, so your code
truly starts, and truly stops, before getting started again?

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
Foust
Sent: Monday, August 09, 2004 6:55 PM
To: Access Developers discussion and problem solving
Subject: RE: [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
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list