Convert Access 97 to 2000

[Derek Riley]

I have been using Access97 for some time now and decided to upgrade to 2000,

the problem is when I convert it to 2000 I get the following message "There
were compilation errors during the
conversion" it looks like it is due to the DAO 2.5/3.5 reference.

Is there a conversion utility that I can run to convert it to DAO 3.6 to run
in Access 2000

There seems to be a lot of changes required in the module where it is using
DAO 2.5/3.5

Many thanks
Derek.

[Danny J. Lesandrini]

Can you solve the problem by just adding a reference to DAO?
If not, could you post the code that's giving you trouble. I don't
think there's a conversion utility out there. You'll have to do it
one at a time.
--

Danny J. Lesandrini
dl*********@hotmail.com
http://amazecreations.com
"Derek Riley" <ma**@rydel.demon.co.uk> wrote in message
news:bq*******************@news.demon.co.uk...

I have been using Access97 for some time now and decided to upgrade to 2000,
the problem is when I convert it to 2000 I get the following message "There were compilation errors during the
conversion" it looks like it is due to the DAO 2.5/3.5 reference.

Is there a conversion utility that I can run to convert it to DAO 3.6 to run in Access 2000

There seems to be a lot of changes required in the module where it is using DAO 2.5/3.5

Many thanks
Derek.

[Larry Linson]

My recollection is that I only had a few problems converting databases from
97 to 2000. Possibly some subset of those could have been avoided had I been
careful to make certain that I had no compile errors in the A97 databases.
At least one of the errors was easily fixed by copying and pasting the code
that had not been converted. Also, as far as I know, Access 2000's convert
function works OK. And, conversions always carried forward the DAO
reference, in my experience.

My question would be, at this late date, why convert an A97 database to A2K?
I see virtually nothing to be gained by such a converstion, and would
suggest convert to Access 2002 or 2003, or just leave it in A97.

Larry Linson
Microsoft Access MVP
"Danny J. Lesandrini" <dl*********@hotmail.com> wrote in message
news:bq*************@ID-82595.news.uni-berlin.de...

Can you solve the problem by just adding a reference to DAO?
If not, could you post the code that's giving you trouble. I don't
think there's a conversion utility out there. You'll have to do it
one at a time.
--

Danny J. Lesandrini
dl*********@hotmail.com
http://amazecreations.com
"Derek Riley" <ma**@rydel.demon.co.uk> wrote in message
news:bq*******************@news.demon.co.uk...

I have been using Access97 for some time now and decided to upgrade to

2000,

the problem is when I convert it to 2000 I get the following message

"There

were compilation errors during the
conversion" it looks like it is due to the DAO 2.5/3.5 reference.

Is there a conversion utility that I can run to convert it to DAO 3.6 to

run

in Access 2000

There seems to be a lot of changes required in the module where it is

using

DAO 2.5/3.5

Many thanks
Derek.

[David W. Fenton]

bo*****@localhost.not (Larry Linson) wrote in
<%A****************@nwrddc02.gnilink.net>:

My recollection is that I only had a few problems converting
databases from 97 to 2000. Possibly some subset of those could
have been avoided had I been careful to make certain that I had no
compile errors in the A97 databases. At least one of the errors
was easily fixed by copying and pasting the code that had not been
converted. Also, as far as I know, Access 2000's convert function
works OK. And, conversions always carried forward the DAO
reference, in my experience.
I've never had an error in converting an A97 database to A2K.
My question would be, at this late date, why convert an A97
database to A2K? I see virtually nothing to be gained by such a
converstion, and would suggest convert to Access 2002 or 2003, or
just leave it in A97.

Well, A2K may be what is installed on the client workstations, as
it is with a very large number of my clients. I do not have *any*
clients running any later version of Access, as a matter of fact.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc