Access crashes when I try and open VBA.

[Zorkmid]

Recently I have been bothered by the error:

"microsoft access has encountered a problem and needs to close. we are sorry for the inconvenience."

This happens each time that I try and open the VBA window. Restarting doesn't seem to do anything and this problem occurs on all workstations. I don't even know where to start to fight this issue.

Any ideas?

-Z

 

[boblarson]

Which version of Access are you using and what service pack level as well?

 

[ByteMyzer]

Does it happen with every database file you open, or only with one file?

If it only happens with one file, then the file is corrupted. You will need to create a new Blank file and import all of the objects from the previous file.

 

[Zorkmid]

I have tested a couple of sample DBs from the internet and I get the same error in all files.

I am using access 2003 service pack 3.

-Z

 

[boblarson]

Try adding this hot fix as it seems to have the potential to fix what ails you:
Post Office 2003 SP3 HotFix

 

[Zorkmid]

Thanks, I'll have my IS dept. check if that has already been added or install it now.

Anything I can try in the meantime?

-Z

 

[boblarson]

Anything I can try in the meantime?

Not that I know of.

 

[Zorkmid]

Here's a bit of new info.

When my colleague logs in to my workstation with his account, he has no trouble opening the code editor. Seems like the problem may be tied up in my user account?

-Z

 

[ByteMyzer]

Interesting. Your original post said, "this problem occurs on all workstations". Does it occur on all workstations only on your login as well?

 

[Zorkmid]

Yes, when I log into my colleague's workstation, I get same error.

 

[boblarson]

Do you have all applicable permissions on the folders where the apps reside (Read/Write/Delete)?

 

[Zorkmid]

Im not sure what you mean by apps. I have access to where all the files are stored etc. Same level of access that my colleague has that doesnt receive any of the crash errors at least.

-Z

 

[boblarson]

If they can log into your machine and it works for them and you can log into their machine which works for them and it doesn't work for you then I would contact your Network Admins and have them try to figure out what is different about your login and your co-worker's.

 

[Zorkmid]

That is exactly the case, I had a hard time getting that into words!

 

[Zorkmid]

Ok,

IS dept. has finally gotten around to looking at this error, have installed the hotfix, given me a new machine, re-imaged my username and I STILL get the error in my database, as well as any access database when I try and open the vba editor. They can't seem to fix the issue for me.

I'm really stuck here, database dev is part of my duties at work and at present I can't even get VBA open. If anyone has any ideas at all to help me out, I'd LOVE to hear them.

-Frustrated in Canada,

Zorkmid

 

[Zorkmid]

Just a note:

I seem to be able to open VBA editor in Excel just fine.

-Z

 

[Zorkmid]

Bump. I'm really stuck here. Are there any user settings or general access settings that I can play around with and see if that helps?

-Z

 

[Zorkmid]

Just an FYI that I have had this issue resolved (at least for now). The network admin created me a new profile and it seems to work now. He says that the cause of the problem had something to do with the code in a macro, he said that he had seen this problem before and in that case was able to trace the error back to a single .dll file and replace it, but could not isolate the file in my case. I hope no one else encounters this error, it cost me a solid 2 weeks of DB dev time.

-Z