Vbe6.dll error

[bobfin]

We've been running an Access macro every night for over a year. It updates a linked Access table using OBDC linked tables. But several weeks ago the macro started quitting after several steps. It was usually after a certain step but some nights it was on a different steps. In the morning we see a window asking us if we'd like to send a report to Microsoft about this error. Several times we sent the report, but have never gotten any feedback.

We checked the Event Viewer and found an Offfice 11 application error about the same time every night since this problem started. The error occurs just before the macro aborts. The error message is:

Faulting application msaccess.exe, version 11.0.6566.0, stamp 42cdb33e, faulting module vbe6.dll, version 6.4.99.72, stamp 40b29ba6, debug? 0, fault address 0x000fc0d6.

The link in the message said there is no more information.

On the PC that runs the macro, we've tried powering the PC off and on, running Office Repair and reinstalling Access 2003, but the error still happens. The operating system is Windows XP Pro SP2.

Any help on this problem would be greatly appreciated.

 

[ByteMyzer]

Have you tried compacting and repairing the database itself? Failing that, try creating a new database and importing all objects from the old database.

 

[bobfin]

Neither of these steps changed anything. Scheduling the job earlier just moved the error earlier. I then converted the macro step that runs the query to a RunCode of a VBA function and had error handling set to display the error description. But still nothing displayed except the window asking if we wanted to send an error report to Microsoft. The same error still appears in the Event Log. How do we get a handle on this?

 

[Zigzag]

Have you tried removing and (reinstalling - Registering) VBE6.DLL
Bit of a long shot but it sounds as if you at the long shot stage

 

[Moniker]

This is going to sound weird, but given the bizarre nature of the issue, have you considered that the hardware may be failing? If you're comfortable doing it, "reseat" the RAM, whcih means turn off and unplug the computer, unplug the RAM, wait thirty seconds, and then put it back in completely. Plug the computer back in and see if you still have issues. If so, consider changing out the RAM with a different computer (assuming same model/brand).

I've seen hardware failures cause similar things.