Linking and Exporting Tables

[Dave31]

Hi

I have a database, but its going to be regional (one in UK, one in India and one in North America), as the database is currently on the UK server, the other two regions take a while for it to load. I am going to put a database in each region and then export all tables into the other tables of the other regional databases.
Currently, i can manually export a table from one database to a sub-database (just for the exporting and importing stage) and i can import this table to another database. Currently when you import this exported table, it creates a second table, can you have it so it imports the content of the table (you are importing) to the current table (the table you are importing to)? Rather than having a new table.

Sorry if this seems confusing, if you don’t understand, ill try and describe an example to help

Thanks in advance

 

[CEH]

Look into "update queries" and "append queries"..... One might suit your needs.

 

[Dave31]

Ok, thanks, 'Append Queries' could work as i could copy all records in all tables (effectively). But the main question is, as the 3 backend databases are not linked in anyway (I don’t know if you can link 2 (or more) database applications together) so is it possible to append queries to copy all records in all tables and then send these records to the other databases across a network?

 

[boblarson]

Replication might be your answer. My database didn't have that great of a distance, but we did have two locations (Portland, Oregon and Sacramento, California) that needed to be using the same Access database. I set up the database this way:

1. Master database backend on the server in Portland.
2. Replicated backends on each user's computer in Sacramento.
3. Each user had their own copy of the front end and linked to their replicated backend.
4. Since I had Office Developer 2000, I had Replication Manager 4.0 so I was able to use that to set a synch schedule of every 15 minutes so everyone was synched up frequently. This database was not time critical in the sense that if a transaction occurred then the others had to know about it immediately. Rather, it was updated several times throughout the day, but a 15 minute window was fine.

The benefit I found for having each user have their own replicated backend was that I could set the path in my master frontend and I didn't have to set the links for each user as we put them all under C:\HDCC and so the links all worked regardless of which location you were in and I didn't have to update the link (which is a pain) for the Sacramento folks.

 

[Dave31]

Thanks for that bob, although, i only have Office 2003, do you know if there is a way similar to the replication manager? as synching isnt too much of an issue, just once a day would be fine, is there a manual way of synching?

 

[boblarson]

Yes, you can manually sych by going to Tools > Replication > Synchronize Now

 

[boblarson]

You could also do it programmatically via code (not sure what the code is, but it might be here in the forum) and set it to do it via a timer.

 

[Dave31]

Ah, thanks i shall try using that. Just out of interest, is it possible to write some vb code to synchronize say everytime somebody logs into any front end of the system?

edit: ah, just saw your second post i shall have a look on the web

many thanks for your help