Help Me!

[chad]

When we upgraded from Access 97 to 2000, it seems, when I
create a new database, some of the built-in functionality
of Access is not available. I can copy an old database
(one that was converted from 97 to 2000) and the
functionality is there. Are there references I should set
or do we all have a bum load of Access?

 

[Wayne Morgan]

What functionality appears to be missing?

By default, Access 2000 uses ADO instead of DAO. You may need to set a reference for DAO.
Also, when you DIM an object, such as a recordset, specify which of the two it is.

Example:
Dim rst As DAO.Recordset

 

[chad]

One of the this that doesn't work is the following simple
piece of code:

Set r = CurrentDb.OpenRecordset("SELECT DISTINCT Year
([DateOut]) AS Yr FROM tblAbsences ORDER BY Year
([DateOut]) DESC;")

The error that is generated is "Type mismatch" (Error code
13). It works fine in a database that was converted from
97 to 2000, but when I put this piece of code in a
database that was newly created, it flops.

Wayne: I know what you mean about having to specifiy DAO
or ADO before the Recordset, but I don't even get
IntelliSense after typing DAO.

-----Original Message-----
What functionality appears to be missing?

By default, Access 2000 uses ADO instead of DAO. You may

need to set a reference for DAO.

Also, when you DIM an object, such as a recordset,

specify which of the two it is.

 

[Albert D. Kallal]

You did check the references right?

whack ctrl-g, and then go tools->references.

You need to add the

Microsoft DAO 3.6 Object Library

I am sure you took a quick look at the referances in the databases that you
converted, and they worked ok. Compare the two.....

Regardless, you need the above to be set, and in fact you should move it
higher then the ADO ref...