Transferring data between Access databases

  • Thread starter Thread starter DaveFrag
  • Start date Start date
D

DaveFrag

I've updated the code within a new version of my Access 2003 application and
need to transfer all the tables from the previous version of my Access
application to my new Access application. How could I transfer the data
contained within ~50 tables from the previous Access application to the new
Access application in an automated way so that I can allow the user community
to perform the updates themselves?
 
When you say that you have updated your code within a new version, are you
using a front end and back end design to your database?

You can always use the File...Get External Data...import....and import in
all your tables if you wanted to go that route...
 
The database doesn't use a front end and back end design. If I were to want
to learn how a front and back end design works, can you suggest where I can
view documentation that would help?

I've thought about importing the data, and that may be the way to go, but I
would like to understand best practice on how this should be done.
 
Front end and back end design is used for databases where there may be a
mutli user environment. The backend of the database is placed on a network
drive like a G: or M:(whatever your shared drive is called) and the front end
is placed on each users C drive or desktop (not a shortcut but an actual
copy). This allows a database that works quicker and if you needed to make
design changes you can make a design changes to your Front End copy and then
have the users on your system upload a newer copy or you can have code be
placed to force the users to upload the most recent copy upon login.

Here is a link to some more info: http://allenbrowne.com/ser-01.html
or here are some other helpful tips by Allen Browne:
http://allenbrowne.com/tips.html
 
DaveFrag said:
The database doesn't use a front end and back end design. If I were to want
to learn how a front and back end design works, can you suggest where I can
view documentation that would help?

I've thought about importing the data, and that may be the way to go, but I
would like to understand best practice on how this should be done.
Click to expand...

You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite
nicely.

I use Compare'Em
http://home.gci.net/~mike-noel/CompareEM-LITE/CompareEM.htm to
generate the code to update the tables, fields, indexes and
relationships in the BE MDB. It has it's quirks but does work.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Back
Top