Upgrading from Access 2000 template to Access 2007 template

[Steve Kirk]

I've been using the Time and Billing template in Access 2000 format for many
years and now I want to upgrade/migrate to the Access 2007 version.

I don't want to have to rekey all my timesheets for the last 5 years so is
there a way of migrating the data? The schema seems to have changed so it's
not as easy as cut and paste or import the old database.

If the author of the template reads this - do you have anything that would
help?

Regards

Steve

 

[tighe]

Steve,

i am sure there are more comoplicated answers, but our firm moved to AC2007
a while ago. there will be a conversion from 2000 you can do, to then gain
the new resources that 2007 has. i dont believe you will have to rekey
anything, excpt for when implementing new features of 2007.

hopes this helps and addresses your question.

 

[Dick Watson]

I suspect the Templates are really considered just "Starting Points" for you
to depart from. So a new starting point in ACC07 is just that. Short of
engineering the migration yourself--I haven't looked at the schema in that
template, but if you started a new database based on the new template, some
linked tables and append queries should be possible--you probably have a lot
of choices.

Your best bets are probably just leaving the old data in the old file
designed using the old template and starting from now in the new template in
a new file, or just migrating the old file to the ACC07 format but retaining
the design that came with the old template. Of course, ACC10 will be here in
a few months, so the merry-go-round will spin again.

 

[Steve Kirk]

Thanks Dick - I think you are probably right to suggest starting from a blank
database as manually 'upgrading' the database is beyond my capabilities at
the moment

Steve

 

[pietlinden]

Thanks Dick - I think you are probably right to suggest starting from a blank
database as manually 'upgrading' the database is beyond my capabilities at
the moment

Steve

FWIW, I would probably start by getting Allen Browne's code to print
out an enhanced relationships diagram for each database. Then at
least you know the types and sizes of all the fields in each table.
Then at least you will know before doing anything where you may run
into trouble. After doing that, you will know which fields have to be
modified, and the order in which you must do the importing in order to
keep the relationship integrity.