Need to move database

  • Thread starter Thread starter Bonnie
  • Start date Start date
B

Bonnie

We use Access for a membership database. My organization
has been using a version of Access that is at least 5 yrs
old (Access 2.0??) & now wants this put on another
computer (not networked), Access 2002 onboard, where
internet access is available. I have attempted to copy to
file several times without success. Any tips,
suggestions, or hints? I really do not want to have to
enter over 20,000 records manually. What problems should
I anticipate jumping so many versions?
 
How big is the Access 2.0 database? If it is less than about 10 MB,
zipped, and you have internet access on both computers, you should be
able to send it to yourself as an email attachement. If all else
fails, install the HD from the old system temporarily in the new one
and copy the database over. I believe that Access XP can read and
convert Access 2.0 database files, though I have never tried it. If
not, you will need to export the Tables from the Access 2 database (I
would suggest using comma separated text format), move the exported
data over in the same sort of way and import them into a new Access XP
database. In this case, you will have to recreate all the Forms and
Reports from the old database, too, but this sounds like a reasonably
simple application.

We use Access for a membership database. My organization
has been using a version of Access that is at least 5 yrs
old (Access 2.0??) & now wants this put on another
computer (not networked), Access 2002 onboard, where
internet access is available. I have attempted to copy to
file several times without success. Any tips,
suggestions, or hints? I really do not want to have to
enter over 20,000 records manually. What problems should
I anticipate jumping so many versions?


Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher
 
Bonnie

I'd suggest that you re-compile your Access 2.0 db before attempting to
import/convert. This will minimize the issues you face.

Access 2.0 ran under, I seem to recall, 16 bit Windows. With more recent
versions, Windows is 32-bit. If your old (2.0) db had any API calls in code
modules, they may not function properly until converted to their 32-bit
counterparts.

The VERY first thing to do is back up your application and data!

It is quite do-able -- you are not the first to face this. You should be
able to make the conversion without having to re-enter the data.
 
Back
Top