I have been working with one particular database - my Repair Database
- which is an order entry / shipping program for selling repair parts
for our company.

From time to time management asks me to go in, and add new features,
or change something. Unfortunately, 2 times in the last week, I've
had to go to a backup, or a MUCH older copy in order to get the
database to open correctly. even if I compress and repair, it still
doesn't fix the problem. I know the trick about copying all the
objects into a new database, and I guess I haven't done that yet
because it's such a huge database. the problem is intermittent,
although it seems to rear it's head after several hours of intense
coding, right before I go to back up what I was working on. Since it
won't repair, or open, I'm forced to go back to a previous version.
of course MS Access gives me this very helpful information as to what
went wrong... anyone want to take a stab at decypering this for me?

Thanks in advance!

-Brian Prenovost


Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 14.0.6024.1000
Application Timestamp: 4d83e4fc
Fault Module Name: VBE7.DLL
Fault Module Version: 7.0.16.19
Fault Module Timestamp: 4d430aec
Exception Code: c0000005
Exception Offset: 00023081
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
LCID: 1033
skulcid: 1033

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our
privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

On 22/12/2011 18:49:32, BrianDP wrote:
Are you using Office 2010 with the SP1 update, in which case, view the thread
started on 23rd November "Re Access 2010 SP1 VBA Errors

Phil

On Dec 22 2011, 6:32*pm, "Phil" <p... (AT) stantonfamily (DOT) co.uk> wrote:
Son of a gun..

Microsoft(R) Access(R) 2010 (14.0.6024.1000) SP1 MSO (14.0.6112.5000)

HA!

Thanks. I thought I had looked at that before, but obviously not.

Happy New Year!

-BrianDP