GPF, IPF, Fatal Exception when printing VBA code, exiting Zoom, etc.

[wrs3]

Checked KB and this forum, no help on these:

Config: W98 384MB RAM, OFF2000SR1a, Jet Engine 4.0SP5, VB 6.0

Failure 1. [Windows] Fatal Exception 0E at 015F:BFF9DBA7
Occurs
Going to VBA codepane window from Acc2000 DB screen. Pane opens, few seconds pass, then error.
Failure 2. System hangs when asked to print code from codepane window from VBA in ACC2000
Failure 3. [F1]
Occurs
After exiting Zoom box on a Query design grid (for field). Starts to return from Zoom close, then error.
Failure 4. [MsAccess] This program has performed an illegal operation and will be shut down
Details
IPF in msaccess.exe at 015F:30045745
Occurs
With VBA editor open, when attempting to open form in design view
Failure 5. [F4]
Details
GPF in user.exe at 000c:00001453
Cascading “illegal operation” errors after close, need to reboot
Occurs
Saving code module from VBA codepane with ACC2000 open

Any thoughts?

Thanks.

 

[ghubbell]

Comment out all your code and try to run access again. If sucessful your code is at fault, if not you either have a bad DB or bad Access/VB stuff somewhere...Reload Access in this case. If it is your code go at it slowly and find where it is tripping. Try copying all the DB objects to a brand new DB.... I had a form once that for the life of me was perfect, but something in it's "genes" was baaad. I did almost all of the above and eventually had to pitch even the recopied form and rebuild it. Gremlins! Gord
ghubbell@total.net

 

[SteveR77]

One other crazy long shot before you attempt to reload. If your video display is set to a high resolution try backing it down to VGA and see if the same things occur.

If this works then there is a video driver conflict and hopefully the maker of the card or MS will have a driver that will solve this issue for you.

Good luck.

Steve

 

[ErikZ]

Do you have your printer set up in windows? I was having a hell of a time working on my laptop because I had no default printer.

Later,
ErikZ

 

[wrs3]

Thanks guys.

Some new thoughts that might help others, and seems to have reduced the IPF/GPF frequency---but, it is still happening.

Apparently when opening the VB Editor (or AKA the "environment", in any event the VBE), if you don't explicitly close the codepanes, they stay open and require resources (of course). With a big application, that can cause the resources to go so low, that it either directly triggers or exacerbates the problem set identifieed above. (See Article: Q223235 in KB)

And, you have no knowledge of this since when in the database window you open Modules (or, "..." on the event procedure property), ACC2000 just opens VBE with all codepanes as they were (apparently).

So, I closed all these codepanes explicitly, and then try to be diligent to close them again after use, and that seems to be getting me along with fewer failures than before.

I also applied OFF2000SP-2, but it had no measureable effect on this problem.

Responses:

ErikZ: yes, it is my windows default printer.
SteveR77: I will try resetting my monitor.
ghubbell: wow, quite a task! Approximately 50 tables, 100 forms, etc. This may be required, but since I compact and repair every time I close, it is an intermittent---but frequent---problem not related to any one form, and there are a few other steps I want to try first before this step, I will hold off on your suggestion for now.

KB Article Q208488 "ACC2000: How to troubleshoot IPFs in Access" has some potentially promising ideas that sound plausible.

Thanks again for your prompt and thoughtful replies.

 

[ghubbell]

My first words back are create a new db (empty) and import in all your stuff. That will only take about 5 minutes. Now turn the compact on close off! I've had that little wonder do more damage than good, especially on networks! 2000's don't bloat like 97s anyway so you can go in once a week and pull the Db onto 1 computer, copy it, compact/repair, check it and then return it to a server. Gord
ghubbell@total.net

 

[SteveR77]

Thanks for for the feedback and I'm sure that this will prove useful to others in the future.

Steve~