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" <dlesandrini@hotmail.com> wrote in message
news:bqqkle$250ej2$1@ID-82595.news.uni-berlin.de...[color=blue]
> 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
>
dlesandrini@hotmail.com
>
http://amazecreations.com
>
>
> "Derek Riley" <mail@rydel.demon.co.uk> wrote in message
> news:bqqg49$8mk$1$8300dec7@news.demon.co.uk...[color=green]
> > I have been using Access97 for some time now and decided to upgrade to[/color]
> 2000,[color=green]
> >
> > the problem is when I convert it to 2000 I get the following message[/color]
> "There[color=green]
> > 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[/color]
> run[color=green]
> > in Access 2000
> >
> > There seems to be a lot of changes required in the module where it is[/color]
> using[color=green]
> > DAO 2.5/3.5
> >
> > Many thanks
> > Derek.
> >
> >
> >[/color]
>
>[/color]
