vba error

[\00AllenRay\]

When I try to click any button to open any form or try to open the module,
it always give me the following error and then close the mdb:


"Microsoft Access has encountered a problem and needs to close. We are sorry
for the inconvenience."

I click for more information as following:

"Error signature

AppName: msaccess.exe AppVer: 8.0.0.3512 ModName: vba332.dll
ModVer: 3.0.0.7019 Offset: 000b6ff

This is urgent. Please help. Many thanks.

 

[JohnFol]

You could also try creating a new MDB and importing the objects into it. .

 

[Hermie]

When I try to click any button to open any form or try to open the module,
it always give me the following error and then close the mdb:


"Microsoft Access has encountered a problem and needs to close. We are sorry
for the inconvenience."

I click for more information as following:

"Error signature

AppName: msaccess.exe AppVer: 8.0.0.3512 ModName: vba332.dll
ModVer: 3.0.0.7019 Offset: 000b6ff

This is urgent. Please help. Many thanks.

 

[Hermie]

Hi Allen

Does this appear on a replicaset?

Herman

 

[\00AllenRay\]

In fact, I can open this mdb on another PC. For my PC, as long as the mdb
contains the vba code, it gives the error while I try to run the code. I
think there is something wrong with my PC and the access setup. Mine version
is access 97. Please help. Thanks.

 

[\00AllenRay\]

Can anyone please help? Thanks.

In fact, I can open this mdb on another PC. For my PC, as long as the mdb
contains the vba code, it gives the error while I try to run the code. I
think there is something wrong with my PC and the access setup. Mine
version is access 97. Please help. Thanks.

 

[\00AllenRay\]

Can anyone please help? Thanks.

 

[noemail]

Allen,

This is not really a forms question. You might want to try reposting
in microsoft.public.access.

Unfortunately not all problems can be explained or solved even though
obviously there is a reason for them. I've had this happen to me also.
Fortunately we have enough computers here that I could just swap
another one to the user that needed the database.

While it did not always help, you could still try a complete reinstall
of Windows as well as Office, and also check that the problem computer
has the exact same version of Access as a non-problem computer. Do
that by clicking Help ->About on the menu and checking the build
number.

You might also want to go through all the Windows and Access settings
to see if there is possibly something different on the problem
computer that might be causing VBA to crash.

BTW, have you actually tried importing all the objects into a new db
as was suggested to you? This is the very first thing you should try.
If it does not work, try importing everything but the modules and see
if it still crashes. See if you can find, by trial and error, if a
specific object is causing the problem.

Peter

 

[Andreas]

Lets have a look.

1)
You can take a copy of this database onto another PC and it works.
What version Access are you running on that PC?
If it is 97, is it Service Release 2?
What operating system are you running?

2)
The same copy of the database is not running on your PC.
Is it Service Release 2?
What operating system are you running?

Provided both PC's are running a full copy of Access 97 SR2 (rather than
one having just a runtime version) and you are using the same identical
database on both PC's and without any further information available:
1) Repair and Compact the database on the PC on which it is working.
2) If it still does not work on your PC, create on the working PC a new
database and import all objects from the "troubled" database.
3) If this database still does not work on your PC, reinstall Access.

Regards,
Andreas