Hi John,

Thanks for the suggestions. It is true that the error occurs more frequently after printing, but I can also experience it without any printing. That doesn't rule out a memory leak, of course. There could be other code which is causing the problem. My frustration is that I just don't know where to look. There is a lot of code (EXE is over 4MB). My basic question is how does one discover the source of the problem so that it may be fixed?

Another thing that I have noticed is that it happens often while closing a form. The code is spread out among a number of classes and procedures but, in general, it is testing for which tables need updating and updating. Then I hear my local drive going crazy (like lots of seeks?) and then the error occurs. Does any of this help?


>Hi,
>
>We have been experiencing similar problem that I traced to print under windows. It seems that by changing the driver (in my case from 6P to HP III) almost stopped the trouble. I noticed two posting on news that also claimed cures for the dreaded page fault. So far it appears the drivers have a memory leak that cause most of the trouble. We still get the error about once a week so I'm still checking into the problem. I hope this helps.
>
>John