[AccessD] AXP and Error 3310

Believe me, I know that and that was my first thought ... A week ago.  I
checked and double checked to make sure the objects are destroyed. I
personally write code to destroy them right after I write the
declarations,  but I've also checked the code written or edited by the
rest of the crew to see if I could spot anything.  This is making me
crazy because there never is an out of memory message, and memory usage
in TaskManager is normal.  That rhythmic thumping you hear is my head
beating against the wall! 

Charlotte Foust


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


On 5 Aug 2004 at 14:49, Charlotte Foust wrote:

> I have a restart functionality built, shelling out to a restart app, 
> but I want to know what's going wrong, not just paste a bandage on it.

> Has anyone else every encountered (and overcome) this?
> 

When something breaks regularly after hundreds of iterations, it is
almost 
always caused by a memory leak. 

Watch how much memeroy the app is using during execution with Task
Manager or 
PerfMon.

Double check that you are explicitly destroying any object variables you

create.


 
-- 
Lexacorp Ltd
http://www.lexacorp.com.pg
Information Technology Consultancy, Software Development,System Support.



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