Microsoft Visual Basic Unexpected error; quitting

[SUZYQ]

I have an Access database (2000) that was working fine yesterday. Now
when I try to open a VBA code window I get a Microsoft Visual Basic
error message that says "unexpected error; quitting". Nothing I do
will work. I tried compacting and repairing the database. I now find
that the same thing is happening on every database on my laptop. I ran
a virus scan just to be sure, and there's nothing.

Anyone know why this is happening and how to fix it?

 

[Ken Snell [MVP]]

Try repairing your Office installation.

 

[Jim Carlock]

Did you install anything between the time that it was working
and stopped working?

--
Jim Carlock
Post replies to newsgroup.

:
I have an Access database (2000) that was working fine yesterday. Now
when I try to open a VBA code window I get a Microsoft Visual Basic
error message that says "unexpected error; quitting". Nothing I do
will work. I tried compacting and repairing the database. I now find
that the same thing is happening on every database on my laptop. I ran
a virus scan just to be sure, and there's nothing.

Anyone know why this is happening and how to fix it?

 

[SUZYQ]

How? Do I have to uninstall and then reinstall the software?

 

[SUZYQ]

No. Nothing. Any idea why it's happening? The only other thing I
noticed was that my Norton Antivirus software was behaving wierd.

 

[Ken Snell [MVP]]

Control Panel | Add/Remove Programs

Select Office program. Then select Repair option.

 

[Jim Carlock]

There's a VBA update... it sounds like you have some kind of
corruption. I would suggest using an anti-spyware utility, as
well as some other anti-virus tools just to be on the safe side.

Also, if you haven't installed the VBA update, I'd grab the VBA
update, extract the files to a folder and then compare those to the
files that are installed inside of
C:\WinNT\System32
or
C:\Windows\System32
http://support.microsoft.com/?id=822150

Files can be corrupted just by copying them from a website to
your system, or less-likely by copying from your Hard Disk to
a floppy disk, or even more less-likely from one folder to another
folder. Also, if files sit on a hard drive for a long time, there can
be corruption in that respect as well. Corruption happens.

I'd try the VBA update from the link above, and personally, I'd
extract the files, then compare them visually to see what dates
are on the files that are actually in place in the System32 folder.

It's really hard to pinpoint from this end without more information:

Take a look at the following files:
vbe6.dll
in the following folder:
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6

Tell us what the date and version of the file is?

--
Jim Carlock
Post replies to newsgroup.

:
No. Nothing. Any idea why it's happening? The only other thing I
noticed was that my Norton Antivirus software was behaving wierd.

 

[SUZYQ]

I mispoke a little bit. I am running Office 2003. The database where
this problem first started was in 2000 -- now it's any database on my
laptop. It must be something with this machine, because when I copied
the database to another computer, the VBA window opened OK.

I do have Norton Internet Security. When I ran a scan, there were no
viruses. However, I must add that the problem with VBA started at the
same time as Norton Internet Security kept prompting me to confirm a
rule it was setting up (normal occurance), but then it kept popping up
over and over (not normal occurance).

So the version of the dll that I have is 6.4.99.72 and was dated
5/24/2004.

I have since uninstalled and re-installed office. The problem is still
happening. I have also run a defrag and it's still happening.

Any help is greatly appreciated!!!

 

[Jim Carlock]

Perhaps turning the Norton product off (unloading it) to see
if the problem goes away might be the easiest thing? Let us
know what the results are?

A more permanent fix might be to uninstal the Norton product
and see if the problem goes away, but we'll leave that alone
for the moment.

That version of the vbe6.dll file looks proper. The link that I
used to verify that...
http://support.microsoft.com/dllhelp/

On that page you can select by file only in the first listbox,
then type in:
vbe6.dll

And Microsoft will happily give you all version information
for that file. I don't know if you like that type of technical
gibberish... ;-) but in case you do, there it is.

Personally, I don't use any Norton products that I know of
right off the top of my head. I did try some of their products
in the past but that was 10 years or so ago.

Let us know what happens?

--
Jim Carlock
Post replies to newsgroup.

:
I mispoke a little bit. I am running Office 2003. The database where
this problem first started was in 2000 -- now it's any database on my
laptop. It must be something with this machine, because when I copied
the database to another computer, the VBA window opened OK.

I do have Norton Internet Security. When I ran a scan, there were no
viruses. However, I must add that the problem with VBA started at the
same time as Norton Internet Security kept prompting me to confirm a
rule it was setting up (normal occurance), but then it kept popping up
over and over (not normal occurance).

So the version of the dll that I have is 6.4.99.72 and was dated
5/24/2004.

I have since uninstalled and re-installed office. The problem is still
happening. I have also run a defrag and it's still happening.

Any help is greatly appreciated!!!

 

[SUZYQ]

Thanks Jim. I resorted to uninstalling the Norton Internet Security
package. I'm still having the same problem. Unless you can suggest
something else, I may have to resort to wiping my hard-drive and
starting again. The only good news is that I don't have a ton of stuff
on this machine.

Thanks, Susan

 

[Jim Carlock]

I'd try this:
Here's the link to the full Office 2003 Service Pack 1...
http://download.microsoft.com/downl...4f731/Office2003SP1-kb842532-fullfile-enu.exe

The page that presents it and describes it:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9C51D3A6-7CB1-4F61-837E-5F938254FC47

It's a huge file so it might take a while to download. You'll want
to make sure you know which folder you're saving it to. Give it
a smaller name... maybe "kb842532.exe" (without the quotes).
I would save it in a folder structure something like:
C:\DL\Updates\Off2003\SP1\

The path tells you exactly what the file is and the kb name is
just a general way to find the file again at Microsoft:

After you've downloaded that file, Cut the vbe6.dll from the
following folder:
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6
and move it to an empty folder:
C:\Backup\

NOTE: After you cut it and move it to the backup folder...
make sure it doesn't pop back up inside of:
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6

because Microsoft has WFP (Windows File Protection) and
WFP protects certain files, if they are deleted from their proper
location (the folder above in this case), it automatically replaces
them. IF that happens, you'll want to go to

C:\Windows\System32\dllcache
or
C:\Winnt\System32\dllcache

One or the other, you shouldn't have both folders in place, unless
you have Windows 2000 AND Windows XP installed on the
same computer, which I don't think is the case, but I'll mention
for your benefit. It's kind of funny to watch a file reappear
after you delete it. It's like a ghost inside the computer. <g>

IF that happens, delete the vbe6.dll from the dllcache folder.

What a pain, heh? <g>

Feel free to ask any questions. I tried to not leave anything
out, but if you have question about why, be as specific as
you can. I was once in a similar situation as yourself. In
fact, many times. <g> It shouldn't hurt to try this.

HTH

--
Jim Carlock
Post replies to newsgroup.

:
Thanks Jim. I resorted to uninstalling the Norton Internet Security
package. I'm still having the same problem. Unless you can suggest
something else, I may have to resort to wiping my hard-drive and
starting again. The only good news is that I don't have a ton of stuff
on this machine.

Thanks, Susan

 

[SUZYQ]

Jim, thanks for your help, but it just didn't work. I ended up
reinstalling Windows XP and Office 2003 and my Norton Internet Security
2005. All seems well now.