If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
How syncronise content of one table in 3 standalone databases?
Hi there,
I am looking for some suggestions, options, which is the best way to approaching this issue (please see below). I have a masters School table contain schools details. Due the a lack, on behalf of user database knolledge, a decision was made, to make this table available in 3 database, rather than linking it to the 3 databases form one back end. (I known..., but !#@%&*) Ok, you guested the problem: to sychronise and have this table (content) the same in all 3 databases. Can you give me some suggestions how I can accomplish this? I work with access 2k. one methode I though of is, to added a row if a new row is added and than update it in all other databases from the main database. 2nd)methode: to run an export (with overwrite to the 2 remaining databases. This way I ensure the contents remains the same in all 3 databases. but.......................... Kind regards Norman |
#2
|
|||
|
|||
How syncronise content of one table in 3 standalone databases?
On Mon, 31 May 2004 17:31:27 -0700, "normanf"
wrote: I have a masters School table contain schools details. Due the a lack, on behalf of user database knolledge, a decision was made, to make this table available in 3 database, rather than linking it to the 3 databases form one back end. (I known..., but !#@%&*) Ok, you guested the problem: to sychronise and have this table (content) the same in all 3 databases. If you REALLY can't link the three databases over a LAN, the next best option is "Replication". It does exactly this - lets you create a "master" database and, from it, any number of "replicas". You can enter and edit data into the replicas, and then run a procedure to synchronize them. It is a complicated process, not for the faint hearted (if your IT people think linked databases are hard they haven't seen anything yet!); there's a good FAQ at http://support.microsoft.com and a lot of information at http://www.trigeminal.com. Note that it's generally considered a Very Bad Idea to replicate a database containing any forms, reports, or code - you split the database using the Database Splitter Wizard, and replicate only the backend. Good luck! John W. Vinson[MVP] Come for live chats every Tuesday and Thursday http://go.compuserve.com/msdevapps?loc=us&access=public |
Thread Tools | |
Display Modes | |
|
|