Map old data to new database

  • Thread starter Thread starter Ralf
  • Start date Start date
R

Ralf

Dear All,

I finished developing a MS Access database. It has been tested by the users
already and should now be used in production. However, errors could still
appear or the customer may wish to extend the set of features.

How to ensure a smooth transition from an old to a new version?

My idea is to send them the new database and to let them execute a macro.
This macro will ask for the location of the old database and map all data
from it into the new database. It should be avoided to copy the tables since
I may have done structural changes.

Is this possible? Or is this an unusual way? The point is that I'm not able
to assist them with that kind of transition. Furthermore, the customer is
absolute afraid of doing something else than entering data.

I would really appreciate if you could share you experiences.

Thank you,
Ralf
 
Ralf

I can't tell from your description whether the application is "split" or
not. If not, consider doing so, as it will facilitate deploying any future
enhancements.

I also can't tell from your description whether the "old" data and the "new"
data structure are identical (so that you are only interested in putting a
copy of the old data in the new container. If so, an approach that's worked
well for me in supporting 'remote' customers is to have them zip 'n ship a
copy of their database/file. When I receive it, I make the changes, then
zip/ship back. They backup their "old" copy and do a simple file copy to
put their "new" version in place.

There are many other details, for example, the folder it goes in, a desktop
shortcut, etc. These will depend entirely on how you've set up your
application.

More info, please...

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Ralf said:
Dear All,

I finished developing a MS Access database. It has been tested by the
users
already and should now be used in production. However, errors could still
appear or the customer may wish to extend the set of features.

How to ensure a smooth transition from an old to a new version?

My idea is to send them the new database and to let them execute a macro.
This macro will ask for the location of the old database and map all data
from it into the new database. It should be avoided to copy the tables
since
I may have done structural changes.

Is this possible? Or is this an unusual way? The point is that I'm not
able
to assist them with that kind of transition. Furthermore, the customer is
absolute afraid of doing something else than entering data.

I would really appreciate if you could share you experiences.

Thank you,
Ralf
Click to expand...
 
Back
Top