Importing tables from one database to another - help please!

  • Thread starter Thread starter FatMan
  • Start date Start date
F

FatMan

Hi all:
I have created a database and have distributed to about 50 clients but now
need to issue an update to the database. When distributed the database
contained a frontend and a backend. Now that I want to issue an update I
have discovered that I had left four tables in the frontend that should be in
the backend and only linked from the frontend.

What I would like to know is how do I move/import the four tables from the
frontend to the backend on the database that have been distributed to the
clients? I can do it on my own computer no problem; the challenge for me is
how to have this happen on the distributed copes.

My line of thought is to do this…
- Send out my update with the new frontend (call it FrontEnd2 for now)
- Create a subroutine on my start up form that will import the four
tables from
the old frontend to the backend.
- FrontEnd2 will have the tables with only a linked connection to the
backend.

I have used the following line of code to import a table into the current
database…

DoCmd.TransferDatabase acImport, "Microsoft Access", "Path\database.mdb",
acTable, "TableToBeImported", oldTableName

How do I import a table into a different database?

I am using MS Access 2000.

Any and all help is greatly appreciated.

Thanks,
FatMan
 
Peter:
Thanks for the utility....it is great!

I have a question and hope you will be able to answer for me.

How do I distribute the "tblVersion" (my table used to store the one record
for ubeVersion) to the clients back end?

This database was developed using Access 2000 developer's edition and was
distributed with a runtime version of Access. Many of my clients wouldn't
have Access and would not be able to add the table to the backend even if
they did have a full version of Access.

Any ideas what I can do?

Thanks,
FatMan
 
The code has a facility built in to do that. It is described in the
section called Add Reference Table. Have a look at that and try it out
(on a copy of your database) and see if it solves the problem. Having
said that, I have not tried it with the run time version of Access but
I don't see any reason why it would not work.

Post back if you still have any problems.

Peter Hibbs.
 
Back
Top