A
Alexander Sinitsin
Hello, All!
MS Office XP/SP2
I have a procedure, that does a hard work - many rows
selected\inserted\updated in many tables. For all this changes transaction
is used. I don't meet any problems at time of development. But when I move
this procedure on production (tables has a lot of data), I meet this
problem.
When procedure fired, ACCESS use 100% of processor time and constantly
consume memory. After a while ACCESS get approximately 80Mb and return
error - insufficent system resources. But I has at least 300 MB of free RAM
and over 3Gb on hard disk.
DAO 3.6 is used. I check my code twice. Any SET a = ... has appropriate
SET a = Nothing.
What things I can check in my project to prevent memory leaks? Is there
problem with ACCESS itself?
With best regards, Alexander Sinitsin. E-mail: al_sin[dog]ukr.net
MS Office XP/SP2
I have a procedure, that does a hard work - many rows
selected\inserted\updated in many tables. For all this changes transaction
is used. I don't meet any problems at time of development. But when I move
this procedure on production (tables has a lot of data), I meet this
problem.
When procedure fired, ACCESS use 100% of processor time and constantly
consume memory. After a while ACCESS get approximately 80Mb and return
error - insufficent system resources. But I has at least 300 MB of free RAM
and over 3Gb on hard disk.
DAO 3.6 is used. I check my code twice. Any SET a = ... has appropriate
SET a = Nothing.
What things I can check in my project to prevent memory leaks? Is there
problem with ACCESS itself?
With best regards, Alexander Sinitsin. E-mail: al_sin[dog]ukr.net