Covert an application in Access 2000 to Access 2003

[Fion]

Hi,
Our company going to upgrade from Microsoft Office 2000 to
Microsoft Office 2003. May I know what are the things I
need to be prepared before the conversion?

Please advise.


Regards,
Fion

 

[Chris Mills]

Lots of things. Prepare yourself by reading these newsgroups, and doing test
conversions of MS-Access before you consider upgrading everyone else (as is
always the case with any upgrade). Such a general question requires a general
answer, it is silly to upgrade without your own extensive testing. There may
be issues which are already known (too numerous to list), or you may very well
come across testing issues which are not well-known or even unknown.

Test it, on some sample target PC's.
Chris

 

[fion]

Thank you. But, I've no choice, its a MUST. Our head office will do the upgrading. No matter what error, it's has to be solved because they don't care.

Thank you very much for you reply. I'll try my best.


Cheers,
Ling Yueh

 

[Chris Mills]

Thank you. But, I've no choice, its a MUST.

Yes I realise that. I myself usually have little control over what a customer
implements, let alone a Head Office!

No matter what error, it's has to be solved because they don't care.

Yes. But you can point out there are known (ie likely) to be many issues with
upgrading Office, and basically it needs TESTING. My own upgrade programs have
required, as a minimum, at least 2 months testing on up to a dozen independent
PC's. For instance, just because it works on Windows XP does not mean it will
necessarily work on Windows 2000. It may be just the SP level of the Windows,
for all you know...tell Head Office "I Said So!!!" One problem is, every mdb
ever designed uses some features of Access and not others!!!

But you asked for a list of "things to watch for". There are many, and there
is no ultimate list, or any list. Also, Access2003 is relatively new as things
go, earlier versions of Access are much better known!

I'll try my best.

That's all you can do! You can't be expected to know in advance what problems
you may come across. I once quoted $1000 for a conversion to Access2000. I
reckon it actually cost me $50,000!

Chris
(sorry about all the exclamation marks)

 

[John Nurick]

Hi Fion,

There's useful information here - but not enough to remove the need for
testing (in proportion to how important or mission-critical the
application is).

Access 2.0 and Access 97 to Access 2000/2003 conversion
issues/problems/bugs:
http://www.granite.ab.ca/access/conversionproblems.htm

To Access 2002 or 3:
http://support.microsoft.com/?id=319400

To Access 2000:
http://support.microsoft.com/?id=237313

 

[Chris Mills]

testing (...how mission-critical the application is).Well, I read that NASA doesn't put any technology up which is less than 10yrs
old. I mean, that's mission-critical and THEY require up to 10 years testing.
All of us "geeks" think we're mission-critical too of course. Well, MS-Office
fundamentally conflicts with "mission-critical", is what I've come to think.
Imagine Neil Armstrong struggling with his controls, running out of fuel, and
then getting an Access "Do you want to submit this report to Microsoft?"

Thanks for all the helpfull URLS.
Chris

 

[fion]

Thank you very much. I'll take a look on them...

Cheers,
Fion