By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,304 Members | 3,132 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,304 IT Pros & Developers. It's quick & easy.

Hope someone can help a nube to access 2000

P: n/a
I have done a LOT of databases in access 97 but I am new to access
2000.
We are S L O W L Y converting over.
Yesterday I had a 97 database that I had to run the converter to 2000
and everything works fine. I thought this is not tooo bad so far.
BUT everyone else in the co that got a copy and converted it on their
system had big problems.
First when they ran the database a vb code view window was open in the
background.
Second some of the routines that worked on my system would not work on
theirs. Was this because of the vb code window being open?

I am now sending them my converted db and hope that it works on their
system like it does mine.

big thanks for any help on what I did wrong.

Is there a good book for someone moving from 97 to 2000 that also
explains how to list converted code and what didn't compile correctly
in the change?

again thank you for any and all help

Jerry

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
The first thing to check in the conversion is the DAO/ADO problem. Access 2000 and above
use ADO by default. Check the References (open a code window and go to Tools|References)
and check to see the Microsoft DAO 3.6 Object Library is selected. If v3.5 is selected,
uncheck it and scroll down to check the new one.

Next, the references are used in the order that the checked ones are listed in the window,
hence the up/down buttons. The better way around this is to specify in your Dim statements
which to use instead of relying on this order. To do this you will need to modify all of
the Dim statements for DAO objects.

Example:
Change
Dim db As Database, rst As Recordset
To
Dim db As DAO.Database, rst As DAO.Recordset

You should be able to do this using the replace window (Ctrl+H)
Search For: As Recordset
Replace With: As DAO.Recordset
Search: Entire Project

Do this for every DAO object (database, recordset, querydef, field, tabledef, etc.)

After doing this, if you still have problems, let us have a few more specifics on what the
errors are.

--
Wayne Morgan
Microsoft Access MVP
"sparks" <sp****@here.com> wrote in message
news:ua********************************@4ax.com...
I have done a LOT of databases in access 97 but I am new to access
2000.
We are S L O W L Y converting over.
Yesterday I had a 97 database that I had to run the converter to 2000
and everything works fine. I thought this is not tooo bad so far.
BUT everyone else in the co that got a copy and converted it on their
system had big problems.
First when they ran the database a vb code view window was open in the
background.
Second some of the routines that worked on my system would not work on
theirs. Was this because of the vb code window being open?

I am now sending them my converted db and hope that it works on their
system like it does mine.

big thanks for any help on what I did wrong.

Is there a good book for someone moving from 97 to 2000 that also
explains how to list converted code and what didn't compile correctly
in the change?

again thank you for any and all help

Jerry

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.