98 to 2000

[Rick]

the company I work for is standardizing to office 2000.
the payroll and cost tracking databases I have created are
in 98. The payroll side is split into a front and back
and compiled end while the cost system is all one database
and is not compiled. anybody have suggestions for what
problems i might run into when i convert them?

Thanks

 

[Ronald W. Roberts]

the company I work for is standardizing to office 2000.
the payroll and cost tracking databases I have created are
in 98. The payroll side is split into a front and back
and compiled end while the cost system is all one database
and is not compiled. anybody have suggestions for what
problems i might run into when i convert them?

Thanks

I think you mean 97. You need to compile them in 97 to make sure they
are error
free. After you convert them, check the references for a missing
reference for the
DAO lib's.

You may have some problems with the bang and dot (! and .). I did on
one conversion

Ron

 

[david epsom dot com dot au]

Conversion from 97 to 2000 is supposed to be painless. 2K
is slower, but conversion problems arise only when you have
VBA project corruption, Access 2.0 compatibility, Network
problems, or unusual applications.

We had particular problems with deeply embedded SQL/DAO/UDF's,
EVAL's, #IF/#EndIf, Deliberate Exceptions (On Error), and
implicit type conversion in DAO parameter queries.

You must have at least SR1 for Office 2000: the first release
of Access had many problems. Office 2000 is now on SR3.

You also need to disable and avoid the A2K specific features
(AutoCorrect, DataSheet Name, etc)

And you should look at Tony's Access Tips, particularly
http://www.granite.ab.ca/access/performancefaq.htm

(david)