Access 2007 finds errors

[Jim Gainsley]

We just installed Office 2007 to replace Office 2003. We have a database
which we've used for a long time in 2003, that was originally created in
Office 95 years ago. Office 2007 doesn't like it, and complains of some VB
errors and a reference to a UTILITY.MDA. What is happening and why doesn't
2007 like it? What is Utility.MDA, we have no file with that name?

Jim

 

[Tony Toews [MVP]]

We just installed Office 2007 to replace Office 2003. We have a database
which we've used for a long time in 2003, that was originally created in
Office 95 years ago. Office 2007 doesn't like it, and complains of some VB
errors

Please post the exact error message(s)

and a reference to a UTILITY.MDA. What is happening and why doesn't
2007 like it? What is Utility.MDA, we have no file with that name?

IIRC that was a file used back in Access 97 days or even 2.0 days.
Remove it from your references. However you will likely then find VBA
which references functions from that MDA which you will have to
correct. Not a difficult task as I recall but a bit irritating.

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/

 

[Douglas J. Steele]

The reference to the UTILITY.MDA likely should have been removed when you
moved from Office 95. It was an add-in used then, but no longer.

You'll need to go into the references and remove it from there.
Unfortunately, I don't have Access 2007 installed on this machine, so I
can't give you instructions how to do that.

 

[Jim Gainsley]

Hey thanks folks! Though I was a programmer I haven't done so for many
years and I've forgotten my way around Access. But with your words and the
very intelligent debugger Help in Access I was easily able to find and
remove the check from the References list. After I did that the other
errors messages also disappeared. The Missing error occurred first in a
Find control, but without correction the Form eventually just locked up so
there must have been other references. At this point, it appears the only
problem for all those errors was the ref. to Utility.mda.

I wish all problems would be this easy to fix. This was an initial try of
Access2007 which we just installed. If the rest of our test on this
smallish database go successfully, we'll try it on our much more complex ERP
database--very scary<g>, but it runs fine under Access2003...

 

[David W. Fenton]

The reference to the UTILITY.MDA likely should have been removed
when you moved from Office 95. It was an add-in used then, but no
longer.

Utility.mda still existed in Access 2000 as wall as in Access 2002.

I think the difference is they've changed the location of it around
several times (in Office97 it's in the Office folder, along with
MSACCESS.EXE, while in A2K, it's in the language-specific folder,
1033, while in my install of A2K2, it's back in the Office10
folder).

I'm not sure why anyone ever needed a reference to it, as its
functionality was always available without a reference, as it's an
Access program component (I've always loved that much of the
Access's functionality is built in itself).

 

[Jim Gainsley]

Thanks David

Utility.mda still existed in Access 2000 as wall as in Access 2002.

I think the difference is they've changed the location of it around
several times (in Office97 it's in the Office folder, along with
MSACCESS.EXE, while in A2K, it's in the language-specific folder,
1033, while in my install of A2K2, it's back in the Office10
folder).

I'm not sure why anyone ever needed a reference to it, as its
functionality was always available without a reference, as it's an
Access program component (I've always loved that much of the
Access's functionality is built in itself).

 

[Tony Toews [MVP]]

Hey thanks folks!

You're welcome.

If the rest of our test on this
smallish database go successfully, we'll try it on our much more complex ERP
database--very scary<g>, but it runs fine under Access2003...

There are reports of relatively minor bugs and differences of behavior
in queries and such. Relatively minor that is until you encounter them
in a production system. I'd wait until SP1 before going live with a
complex app.

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/