Office 97 to 2004 or XP

[Guest]

We have programs written in Visual Basic in Office 97 which use Access and
Excel together. We are considering upgrading. I have been reading some
posts and I see a lot of "I didn't like the upgrade and am reinstalling
Office 97....", etc. I tried to upgrade to Office 2000 and we got a lot of
"can't find variables", so we didn't do it.

Does anyone like the newest upgrades? Did you run into problems with
variables not being recognized when upgrading from Office 97 to Office 2000
or newer?

Can the varialbes problem be solved without having to rewrite all our
programs?

 

[Allen Browne]

A well-written database does not have to be redone when you convert to the
new version. Most of the old things convert smoothly, and - with the service
packs - it is now possible to get A2000, 2002 and 2003 all running well.

There are some traps in the new versions you need to become familiar with,
though. See:
Converting from Access 97
at:
http://members.iinet.net.au/~allenbrowne/ser-48.html

 

[david epsom dot com dot au]

Doing a full conversion from Word 97 to Word 2000 was painful, but
unnecessary. There were only a few things that I had to change to
keep the old Word Basic code (from Word 6) still running.

But you should ask in an Excel group about conversion of Excel VBA.

Access 2000 was very painful on first release. Most of those messages
you saw date from that time. It was not nearly as bad after the first
Office update. But many people think Access 2003 and 2003 are better
than 2000.

I never got a 'can't find variable' message when upgrading anything.

(david)