Having converted my apps from Access 2 to Access 97 I have several
instances of Access 97 crashing, normally when trying to run the setup
code in the dbs.

Now it is crashing when I run the setup, or when I try to compile the
code (single compile or compile and save all)

The details are

MSACCESS caused an invalid page fault in
module VBA332.DLL at 0217:6519eed0.

Repair and/or compact of the dbs has no effect

This has brought work to a halt.
Any help in getting it going again please!
--
Mark Fisher
Add k to end of address if replying by Email

Hi,

Have you installed the Office Service Pack 1?  Also, have you tried
re-registering vba332.dll with RegSvr?

Dev
--
Just my $.001
Please limit questions to newsgroups only!
Dev Ashish
---------------
The Access Web ( http://home.att.net/~dashish )
---------------

:Having converted my apps from Access 2 to Access 97 I have several
:instances of Access 97 crashing, normally when trying to run the setup
:code in the dbs.
:
:Now it is crashing when I run the setup, or when I try to compile the
:code (single compile or compile and save all)
:
:The details are
:
:MSACCESS caused an invalid page fault in
:module VBA332.DLL at 0217:6519eed0.
:
:Repair and/or compact of the dbs has no effect
:
:This has brought work to a halt.
:Any help in getting it going again please!
:--
:Mark Fisher
:Add k to end of address if replying by Email

I (and some others out there) have the same problem.
Installing Office Service Pack 1 does not solve the problem.
Other Access 97 databases open fine and the repair utility does nothing.
It seems the database is corrupted and Access doesn't know how to fix it.
Any ideas?

Thanks,
Scott

Yes I had installed service pack 1, and sp2 for the developers edition.

I tried importing all the objects into a clean dbs and found that 1, and
only 1, form was corrupt. Trying to open this form, or to view the code
in design mode, caused access to crash.

A backup copy of 2 weeks ago was okay, so I got the relevant form from
there.

Thus, problem fixed, but Why did the form get corrupted and cause access
to crash in the 1st place. when will happen again? (2 days after I
release it to the Bank I suppose<g>)

--
Mark Fisher
Add k to end of address if replying by Email

I also tried to import from the corrupted database into a blank new one.
Only the tables and queries got through.  When I tried to import ANY
reports, forms, or macros,  Access crashed.  Service packs do nothing.
Seems to be something with VBA332.DLL.

On another issue, whenever I close a database and then open another one,
Access crashes.

This frequent unstable behavior (even for Microsoft) is certainly annoying
and seems to lead to corrupt databases.  I would certainly recommend having
several recent backups to restore from.

Scott

:Thus, problem fixed, but Why did the form get corrupted and cause access
:to crash in the 1st place. when will happen again? (2 days after I
:release it to the Bank I suppose<g>)

Sorry don't know the "why" of it. Never found a "list" of why a form/report
object gets corrupted or when.

--
Just my $.001
Please limit questions to newsgroups only!
Dev Ashish
---------------
The Access Web ( http://home.att.net/~dashish )
---------------

If you are using Jet 3.51, there is an undocumented switch that might solve
the problem. From Explorer's Run option type..>

msaccess "mydrive:\mypath\mymdb.mdb" /decompile

This only works if you have 3.51, but it is very handy and will often fix
this kind of problem. Enjoy!

THANK YOU.
This "undocumented" switch solved my corrupt database problem.
Why the heck is this switch undocumented, besides {*filter*}about debug modes and
testing?  A developer could actually benefit from a stupid thing like that
w/o wasting time and money.  Microsoft STINKS!

Vehemently yours,
Scott

Scott,

When MS doesn't document something it (usually) means one of two
things...either they aren't sure the function/switch/whatever will be there
in the future, so they don't want you to depend on it and then yell at them
when their next version breaks your app, or it got added too late for the
documentation, print lead times being what they are.

Well, you asked.

    - Rebecca.

What patch or upgrade is this in at is sounds most useful?

--
Mark Fisher
Add k to end of address if replying by Email

also found a way to repeatdly corrupt the dbs.

open a form, run some code, get an error, go into debug mode, fix error
in code, close app.

asked to save changes in form. Say yes.

open any module to compile and save. But.. it is grey out. app is
already compiled and saved. (No it isn't, I just made a change)

Quit access. Go back in.

dbs now corrupt and access falls over. Need to compile and save again to
fix.

Not quite the same prob, but a repeatable bug none the less.
--
Mark Fisher
Add k to end of address if replying by Email

Hi Mark,
I've just tried following your instructions and I can't get the database to
corrupt, which version of Jet are you using? and what is the runtime error
that you are getting in orer to cause this?

I did ask and it still doesn't solve the problem with Microsoft.  Every
app/os they ever developed has bad documentation and bugs due to bad
programming or meeting deadlines (which aren't met anyway).  The "next
version" always breaks apps and isn't compatible with the current ones,
functions documented or not.  Why can't Microsoft make an app that works ON
THEIR OWN OS?  They have billions and all the time in the world,
monopolistically (?) speaking.  What's wrong with at least mentioning these
"unofficial" switches?

Well, there is my spam/flame vs. Microsoft.  My real point is that they have
enough lawyers defending them for putting out crappy software and trying to
control the world.  Expertise, not excuses, is what they need to keep us all
happy.

Scott