Access 2007 right click crash with legacy MDBs

[Mack]

I am experiencing a problem with Access 2007 crashing when users right click
on a form's field which doesn't currently have focus. It only seems to affect
legacy *.mdb databses, particularly those created with Access 2000 or Access
97.

The fault can be demonstrated reliably using the "Video Collection
Database" Access 2000 template from Microsoft.
(1) Load this database into Access 2007 :
http://office.microsoft.com/en-au/templates/TC011817771033.aspx?CategoryID=CT102144001033
(2) Then click on "Enter/View Videotapes".
(3) Ensure your text cursor is in the "Description" field.
(4) Now right click on any field below "Program Name" or "Actor".

This will cause Access 2007 to crash with a 0xC0000005 error code.

Does anyone know of a solution for this problem, or is it a bug that
requires fixing?

If the latter is the case, what is the correct avenue for reporting such
issues to Microsoft?

 

[Tom van Stiphout]

On Wed, 23 Apr 2008 06:36:00 -0700, Mack

I don't have that problem here.
Maybe reinstall A2007?

-Tom.

 

[Mack]

Thanks for your response Tom. Though I've uninstalled/reinstalled Access in
the past to no avail but I just did it again and the crash still takes place.
Any ideas on how I can determine the cause?

-----------------------------
Exception Information
Code: 0xc0000005 Flags: 0x00000000
Record: 0x0000000000000000 Address: 0x0000000030314b6d

AppName: msaccess.exe AppVer: 12.0.6211.1000 AppStamp:46d4aa81
ModName: msaccess.exe ModVer: 12.0.6211.1000 ModStamp:46d4aa81
fDebug: 0 Offset: 00314b6d

 

[Tom van Stiphout]

On Wed, 23 Apr 2008 23:31:01 -0700, Mack

My guess is there are only a handful of programmers on the Access team
at Microsoft that could determine that based on this information and
the Dr Watson log. And they're not volunteering.
My solution in cases like this is to first cover the low-hanging fruit
such as making sure I'm on the latest service pack, run Windows
Updates. Second would be an Uninstall/Reinstall of Office. Third would
be a rebuild of the computer. At least these steps take a known
quantity of time, whereas continuing to tweak things, read up more on
possible causes, etc. takes an unknown quantity of time.

Good luck,

-Tom.

 

[Tony Toews [MVP]]

My guess is there are only a handful of programmers on the Access team
at Microsoft that could determine that based on this information and
the Dr Watson log. And they're not volunteering.

FWIW Microsoft folks pay a *lot* of attention to reported crashes.
They do their best to fix up the problem. It's been my experience
that crashes are frequently, but not always, fixed in the next SP.
(Regretfully there are several A2003 SP3 hot fixes that cure problems
introduced in SP3 so this isn't a perfect process.)

They really do understand the pain it causes.

Microsoft: We Share Your Pain
http://msmvps.com/blogs/access/archive/2007/06/06/microsoft-we-share-your-pain.aspx
for a serious and a humorous approach to this issue.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

I am experiencing a problem with Access 2007 crashing when users right click
on a form's field which doesn't currently have focus. It only seems to affect
legacy *.mdb databses, particularly those created with Access 2000 or Access
97.

What happens if you create an A2000 format MDB. Then, using A2007,
import from the MDB into the new MDB?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Mack]

I have latest service pack, all the latest Windows updates and have
uninstalled & reinstalled Office 2007 still to no avail. I am sorry but a
rebuild or reinstall of Windows is not an option. I would be doing this
almost every week at the rate that this "solution" is proposed as an answer
to software related problems. I know this particulr problem also affects
other users as there have been previous posts here about this issue. So my
only comfort is in knowing that others suffer from it and they too also
have no answer.

Regards, Alan McFarlane.