Creating a "Version 2.0"

message from RKumana on 19 May 2004

I developed an Access database about a year ago (with
much help from the MVPs - thanks!). After using it this
year, I have come up with a number of different problems
with the intial table and data structure and want to
change it. I'm talking about major revisions to tables,
queries, forms, etc. But, I need to keep the data, AND I
need to continue using the database! I'm looking for
insights into upgrading.

Has anyone done something like this?

Is it easier to develop the new version on the side and
then transfer data using some kind of query?

Or is it better to slowly rearrange the data structures
while the database is in use?

The problems are:
1. The database is in continual use. The data will be
modified regularly. It can't be down for more than a week
or two.
2. This isn't my only task, so I can't spend several days
on it at once.

Ideally, I would like to make Version 2.0 up and working
and then map all the existing data (obviously with
changes - will a query work? a function?)

Lynn Trapp replied to RKumana on 19 May 2004

Answers inline below

R Kumana replied to Lynn Trapp on 26 May 2004

thank you.

Although I'm nowhere near ready to do this yet, I'm
assuming an append query is the best way to transfer data
once the new database is ready. Is this right, or do
functions work better for this.

problems
starting point, though.

Archived message: Creating a "Version 2.0" (Microsoft Access Forms)