Undefined datatype

[Gert]

I'm currently doing some minor updates on a VBA program. I'm using Access
2003 SP 3 and I'm editing an Access2000 database without upgrading it to
Access 2003 (because most of my users, use Access 2000). The updates I've
done work fine under Access 2003 but when I try to run the program on Access
2000, I get errors on place where no changes were made. Example: in the line
"Dim db As Database"

Can you help me out?

 

[Allen Browne]

This sounds like a problem with library references:
http://allenbrowne.com/ser-38.html

When switching back to an earlier version, a decompile would also be
worthwhile.

 

[Tom van Stiphout]

On Wed, 5 Mar 2008 04:02:01 -0800, Gert

Good chance you have a missing reference.
Code window > Tools > References

-Tom.

 

[John Spencer]

Try explicitly dimming the item as
Dim db as DAO.Database

Both the ADO and DAO libraries have a Database item.

You also may have to check out the library references
To do its job, Access makes use of various external program and object
libraries. If you move a database from one machine to another, these
references may be "broken".

When this happens, you need to take steps to let Access repair the
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.

Here are MVP Doug Steele's instructions for how to do it:

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing to
suspect is a references problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

Just so you know: the problem will occur even if the library that contains
the specific function that's failing doesn't have a problem.

**** End Quote ****

--
John Spencer
Access MVP 2002-2005, 2007-2008
Center for Health Program Development and Management
University of Maryland Baltimore County
..

 

[Douglas J. Steele]

<picky>
Actually, DAO is the only one to have a Database item. There are, however,
many other items in common between the two models, such as Recordset,
Property, Field and so on.
</picky>