> You may want to try something a little less drastic than deletions.... and
> realize that there is no VBA332 fix (the fix was for VBA232 only, and this
> file is not used by Access 97).
> Try opening the database with the /decompile flag and the shift key held
> down. This fakes Access into thinking that the binary format has to be
> changed, so it decompiles the entire database.
> msaccess.exe /decompile c:\foo\yourdb.mdb
> Michael
> >There is a fix for this on the MS Web Site. Search the site for "IPF" or
> >"Invalid Page Fault" and you should find several technical documents on the
> >subject. The is a simple fix you can download. This is a real problem w/
> >MS Access 95 (my version) and I think 97.
> >The file you download will update the Dynamic Library (DLL) and fix the
> >problem for good. To fix your program for now, delete the newest modules
> >or macros you created until the problem goes away. To open the program and
> >bypass your autoexec, hold down the shift key while clicking the icon.
> >Good luck,
> >AG
> >> I was writing/editing code in an access class module when my database
> >> suddenly died, bringing up the "This program has performed an illegal
> >> operation and will be shut down..." message. Clicking on the details
> >> gives the following further information:
> >> MSACCESS caused an invalid page fault in module VBA332.DLL at
> >> 0137:6517daaa.
> >> ... Register Information...
> >> Now, whenever I bring up the database, it gives me the same error. If I
> >> try to create a new database and import all the data, all the queries
> >> import, one or two forms may import, and possibly one or two class
> >> modules, but then it abends giving me the same error.
> >> I've tried upgrading to the new release of the DAO engine, compacting the
> >> database, repairing the database and several other things, all to no
> >> avail.
> >> MS Support walked through trying several of the above things. Their
> >> response was - gee I hope you had a backup! To add insult to injury, I
> >> found out my nightly backups weren't backing up this database. The last
> >> working copy I have of this is 2 weeks old!
> >> One thing I tried was actually editing out the start-up form in the
> >> database with a hex-editor. Now when I bring up the database, I get an
> >> error stating it can't find the startup form ' ', but I can at least
> >> see things in the database.
> >> When I go to edit a class module now, only a few of the classes can
> >> actually be edited, the others cause this error to occur again.
> >> Anyone had similar problems?
> >> Any suggestions as to how I might salvage the database?
> >> Dean Baskin
Invalid Page Fault in Module VBA332.DLL