Access 2003 to Access 2007

[James Ivey]

I created a simple database on WinXP using Access 2003. Then split it. So
far so good.

I emailed the two files to my data entry person who is on Vista and Access
2007.

When she tries to open the database, she gets this message:
***************************
The application you are attempting to use has a reference that it cannot
resolve to an object, type library, DLL, or external database. Either the
object, type library, DLL, or database was deleted or renamed. Examine the
Available references list in the References dialog box in the Visual Basic
Editor ( Tools menu) to determine if any action is required. If you did not
create this application, contact the programmer or administrator of the
system.
If the reference listed in the Available references list is preceded with
"MISSING:" clear the check box to remove the reference if it is no longer
required. If you still need to use the reference, clear the check box entry
for "MISSING: <referencename>" in the Available references list, and then
create a new reference to the file using the Browse... button. If this is an
installed database application, you may need to reinstall or repair the
application.

These are the error codes I'm getting,,,,,,,,,,,,,,,,audio Controls2.ocx
version 1.0
FPDTC.DLL
VSFLEX3.OCX version 3.0
****************************

I got on the phone with her, but didn't have much luck because it seemed
like the Access 2007 User Interface is a lot different from 2003. She did
not have "File Edit View Insert Tools Window Help", for example.

Help (

James

 

[James Ivey]

Hi Bonnie,

Thanks for replying.

I went to Tools>Macro>Visual Basic Editor
Then in VB Editor Tools>References

I found the two things that reference those two files and removed the
checkmark.

Does that sound right?

James

 

[James Ivey]

Tested Ok for me.

I've emailed her the new Access files with the references removed. Probably
won't hear from her until tomorrow.

Thanks for your help. I hope it works )

James

 

[david]

That fixes the references problem, and makes it run ok, but
if those two objects are used on forms, the forms won't display
correctly.

When you add an object to a form, a reference is added to the
VBA project. This is helpful for programming, but not required
if you don't do any programming to the object - just using it on
a form somehow, perhaps with it's properties referenced in a
query or in another control.

When you remove an object from a form, the reference is
probably not removed - I'd guess that it is left because I don't
think Access counts the number of times you design an object
onto a form.

The VBA project reference causes the VBA project to fail if
the object is not installed. For this reason, it is a good idea to
watch out for unneeded references that Access has helpfully
installed.

(david)