Replication is a big step and only used (in my experience) when users have
laptops and need to syncronise data when back in the office. Why have you
decided to use replication ?
Restoring data across design master/replica isnt something I would dare try
and imagine it to be littered with sychronise conflicts.
Sorry I cannot help, but you might be attempting something a bit to complex
for your skills considering reading some of your other posts on this forum
which ask basic code questions.
"rdemyan via AccessMonster.com" <u6836@uwewrote in message
news:6ae8dae143f4f@uwe...
Quote:
For some of my really important tables, I have backup tables in the
backend
file. The idea is that if a user accidentally screws up data, they can go
to
a form and restore from the backup table (as opposed to having to use a
backup copy of the back-end). In the past, for the table backup
operation,
I was simply deleting all of the data from the table backup and then using
an
append query of data from the main table. To restore, I was simply
deleting
all of the data from the main table and then using an append query of data
from the backup table.
>
But, I've recently decided to implement replication. With replication,
these
delete operations dramatically increase the size of the back-end file.
So,
now I'm thinking I really should do an incremental backing up or restoring
of
data.
>
Can someone help me with code to do this. It would seem to be me that the
idea would be to compare the two tables and resolve any field updates, row
deletions and row additions.
>
Thanks.
>
--
Message posted via
http://www.accessmonster.com
>
