Copy Contents of Tables from one db to another

[Quintios]

I have two copies of a database. One is a working copy and the other is the development copy. What I would like to do is, as updates are made to the development copy and tested, copy the contents of the working copy to the development copy and then publish the development copy.

I did a search and found questions similar to this but nothing that "fits the bill", so to speak.

Is there some code that I could add to a module that would copy all information from all tables from one database to another? I realize that if the table structure changes this might not be possible.

Thanks in advance,

Onwards,

Q-

 

[oharab]

1st thing you need to do is split your database.
There is an add-in built into access which will do this for you. It creates 2 files, the backend or data file, which is just the tables of data, no queries, forms, code, etc.
The other frontend file links to the tables in your backend file and contains all the forms and queries your users will see.

Now when you make changes to the file in your development edition, all you do is link it to the live data file (as opposed to the test data file on your machine) and copy it over the old version. You do not need to copy the data across.
One big advantage of this method is you can give every user a copy of the frontend file onto their local machine, which will cut down on network traffic and make your entire application much more stable.
You can also create several front end files for different areas, perhaps a data input file for the data clerks, a reports package for the MD and a query package for the analysts. All these users can still look at the same data, but have very different needs and styles.
Somewhere I have some code that gives one way of making sure everyone has the latest version of the software. Let me know if you would like me to dig it out.

Ben ----------------------------------
Ben O'Hara
bo104@westyorkshire.police.uk
----------------------------------

 

[Quintios]

Hey, thanks for your help Ben. I think you emailed me about another problem last week regarding getting the contents of Access into MS Word without creating more than one Word.Application. Finally got that one figured out...

If you wouldn't mind digging around for the code, I'd appreciate it. I haven't split the db yet as I'm still developing it, but I wanted to lay the foundation for later when people are actually using it.

In some ways I would like to keep it as a standalone db as usually only one person will be using it (it's a project development database). In that way, they could zip it up and take it home on a floppy and work on it at home. I'll get feedback from folks and find out what would be the best for all in that respect.

So yeah, send me the code. quintios@yahoo.com

Thanks!
Onwards,

Q-

 

[Quintios]

One thing. How do I get the front end to point to the back end? There will be many copies of this thing as there will be one database per project, and we have many projects. There is one database running around that has an INI file with the path to the back end. The user installs the front end on their machine and then modifies the INI file to point to the back end.

I have yet to find a post that will explain how to accomplish this task. I'll start another thread if need be.

Thanks!
Onwards,

Q-

 

[oharab]

bear with me & I'll answer both questions at once.
I've a lot on, so it may be tomorrow by the time I get a spare minute.
If anyone else can help, feel free.

B ----------------------------------
Ben O'Hara
bo104@westyorkshire.police.uk
----------------------------------

 

[oharab]

Have a look at:
faq705-2010

Ben ----------------------------------
Ben O'Hara
bo104@westyorkshire.police.uk
----------------------------------