Invalid Page Fault in VBA332.dll
Make a copy of any form (maybe the corrupted form) in your database,
cancel the original form an rename the copy to the original form name,
then recompile the entire database. If this solution doesn't work, try
to import any form (with
VBA code inside) from any Database (maybe from
your last backup), cancel the imported form after that, and than
recompile the entire database.
Martin Maurberger
Quote:
> I have a large Access 97 database with some 500 tables and a similar
number
> of
> stored queries and forms. The compacted front end MDB is about 21 Mb.
The
> back End in development mode is about 15 Mb
> From time to time, the "Compile all Modules" function does NOT work.
I have
> tried importing the database into a new database, but this does NOT
solve
> the problem.
> Also, on more occasions than I would like, a form is corrupted
somehow. When
> this occurs, the application fails on start up.It returns the message
> "MSAccess caused an invalid page fault in Module VBA332.dll at
0157:6517
> daaa etc etc
> I have not been able to discover, what I am doing that causes a form
to be
> corrupted, nor found any
> way to repair the problem. I simply take backups frequently and go
back to
> the previous backup.
> Can anyone offer any information source which may help me understand
what
> may be occuring.
> I have referred the problem to Microsoft, and am waiting for a
response
> Merv Couper
--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
