API & DAO problems

[Cynthia]

We are in the process of upgrading all of our machines to
office 2000 pro but we have one machine that we have to
keep on office 98 because we can not get an access
database to convert to access 2000 i have tried everything
i can think of. but when i go to save changes to the
database it still does not work. it always sends me an
error with DAO and the API declarations is there any
suggestion ya'll can make
Cynthia

 

[Joel Wiseheart]

One of the problems I found when converting databases is
that if you have any references to DAO objects, you now
have to specify that it's a DAO object. For instance, if
you have:

Dim db as Database
Dim rst as Recordset

You have to change all of those references to:

Dim db as DAO.Database
Dim rst as DAO.Recordset

This is because these objects have equivalents in the ADO
library, which Access tends to assume you want unless you
specify DAO:

Dim db as ADODB.Database
Dim rst as ADODB.Recordset

Also, make sure you have a set reference to the Microsoft
DAO 3.6 Object Library (and possibly the DAO 2.5 / 3.5
library, depending on how old the original code is). In
some instances, I have had to remove and then relink the
reference to get it to work.

Also, prior to conversion, it helps to compile all
modules from the Module | Debug menu, and compact nad
repair the database.

Try those, and see if you can convert it successfully.

When you talk about API declarations, are you talking
about functions that access the Win32API?

 

[Guest]

i'm using windows api utilities in a module. another
coworker created it in access 98 and access 2000 wont
access it at all

 

[TC]

There are about 50 gazillion different error messages pertaining to DAO &
APIs.

Maybe >posting the messages<, might help someone help you?

TC

 

[Joel Wiseheart]

It would help to know which Windows API calls are being
used, and what error messages they generate.

 

[TC]

Which is what I said to her yesterday; but she thinks we all have E.S.P.


TC