Does anyone have an opinion on replication as opposed to simply automatically copying over a master database as new code or changes are made?
My application uses linked tables to a seperate database. All of the tables in the application are for local queries only. Data is copied down from the linked tables to local tables when needed.
I have added a table with a version date. On startup, if the master application version date is newer than the local application version date, the database is automatically copied to the local location. There is no data loss, because all data is in the linked tables. This allows me to make changes to the master and have the changes automatically copied to users.
I know replication achieves the same goal, but it seems a little more cumbersome to setup.
Regan
My application uses linked tables to a seperate database. All of the tables in the application are for local queries only. Data is copied down from the linked tables to local tables when needed.
I have added a table with a version date. On startup, if the master application version date is newer than the local application version date, the database is automatically copied to the local location. There is no data loss, because all data is in the linked tables. This allows me to make changes to the master and have the changes automatically copied to users.
I know replication achieves the same goal, but it seems a little more cumbersome to setup.
Regan
