Transporting Design from computer to computer

  • Thread starter Thread starter Wendy
  • Start date Start date
W

Wendy

OK, a developer question....... how do you transport design changes to
tables, forms, queries, reports from the computer where the design work is
being done over to the production computer without disrupting the existing
formats?

I know how to export them out to a "transfer.mdb" on a floppy or whatever;
and thought that importing them from "transfer" into "production" would work
just fine, but instead I ended up with a copy of each element (e.g., table,
form, query) all named as Table1, or Form1, etc. This defeats my purpose
of being able to make design changes in a test environment.

Again, thanks in advance for all and any assistance.
 
Wendy,

When you import any object of the same exact name and type, Access will
append the suffix 1, 2, ....n. If you want to avoid this, first delete the
existing objects that have the same name as those you will be importing.

Alternately, after importing all the new objects and having Object 1, Object
2...Object n, first delete the original objects and then rename those with
the suffixes to the name of the original objects.

Alan
 
The standard development approach to this problem is to split the
application into just data tables, and another part with the "guts" of the
application.

Thus, we have what is called a Front End, (forms, code, reports etc), and a
back end (just the data).

With this split, then to developer bug fixes, updates etc, you simply give a
copy of the FE to the user, and the data is un-touched.

Splitting the data out from the application is thus the standard practice.

You can read up on splitting here:
http://www.granite.ab.ca/access/splitapp.htm
 
Back
Top