HELP - Urgently

[MyDugs]

I have the following message whenever trying to execute any commands in my Access97 DB.
It was running ok last evening, Access runs any other dbases ok but this only occurs after I open the db I am working on then try to execute a command - even try to save main switchboard form.

MSACCESS caused an invalid page fault in
module VBA332.DLL at 0167:6517daaa.
Registers:
EAX=0000000c CS=0167 EIP=6517daaa EFLGS=00010286
EBX=0044355c SS=016f ESP=0062f0a8 EBP=80000068
ECX=7fffffff DS=016f ESI=00443840 FS=0def
EDX=00000068 ES=016f EDI=0044383c GS=0000
Bytes at CS:EIP:
8b 58 1c 81 e5 fc ff ff 7f c1 ed 02 85 db 0f 84
Stack dump:
0062f0dc 7fffffff 00443840 0044355c 651a339d 0044383c 00000000 00000000 0044355c 00000033 0062f0e8 0044355c 651b4e25 0062f140 651a356e 0044355c Dave

 

[MyDugs]

Sorry forget this - looks as though the class module for a particular form has corrupted, hence crashing when trying to run anything or view object browser. Anyway round this ? Dave

 

[snoopy75]

Sure... step through your code and see where it crashes at, then try and figure out why it crashes. As far as I know, VBA in itself is pretty safe, but if you're doing any API calls, then crashes are more likely.

If you find out which line of code is your problem, post it here and maybe we can help with it.

 

[NormDuffy]

Sometimes access for reasons unknown will refuse to run some code on a form even if there are no errors in the code.
I have found that it often solves these problems if I create a new database and import all the objects. Doing this on a regular basis during developement of large and complex applications is often a safe way to keep access tidy.

 

[snoopy75]

A good idea, but I'm curious.... isn't that exactly what compacting the database does, in essence?