I've had really good luck with this, actually. A
couple of years ago we moved 4 very complex applications for one client from 97
to 2002 with very little issue, and recently did a huge one from 97 to 2003 with
no problems whatsoever.
It obviously makes sense to do a trial run with a copy of
the program and data. Walk through the functionality of the entire thing
and see what you get.
I'd second Dawn's recommendation of importing into a blank
DB of the newer version, as opposed to doing the conversion. I'd also
recommend decompiling after you do the import, using the decompile switch.
Decompile is documented here: http://www.trigeminal.com/usenet/usenet004.asp
Tom Oakes
Personal PC Consultants, Inc.
[EMAIL PROTECTED]
503.230.0911 (O)
402.968.6946 (C)
734.264.0911 (F)
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Olamide...
Sent: Friday, January 13, 2006 2:43 PM
To: [email protected]
Subject: [AccessDevelopers] Migrating access 97 to 2003
plan on migrating quite complex databases from access 97 to access 2003
looking for ideas, tips, pitfalls, references???
i know it will be crazy based on what i have heard about this...
Please zip all files prior to uploading to Files section.
YAHOO! GROUPS LINKS
- Visit your group "AccessDevelopers" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
