|
|
Posted by Query Builder on 04/20/07 14:55
First, Thanks for you input.
I apologize for the confusion. Ed Murphy is correct.
Here is a clear explanation of the situation.
Lets say the table has 10 records.
2 of them have a DeleteDate value in the column.
So, I want the 8 records to be replicated to the subscriber.
If a user goes and updates another record with a value in the
deleteDate, I want that record to be deleted in the subscriber. (Now
out of 10, three of them are marked with a value in the DeleteDate).
Also, if a user goes and removes the DeleteDate value on one of the 3
records, I want that record to be inserted into the subscriber table.
I am going to try the way Hilary mentioned and let everyone know the
results.
Thanks again for the help....
Regards,
Aravin
On Apr 13, 1:00 pm, Ed Murphy <emurph...@socal.rr.com> wrote:
> Hilary Cotter wrote:
> > But I'm a little confused - you say " if i see a value on the DeletedDate, I
> > don't want that record to be picked up for replication."
>
> > But then in the next statement you say "when someone marks the record for
> > deletion (by putting a date on the DeleteDate column), I want that record to
> > be
> > deleted on the subscriber database"
>
> > These sound like mutually exclusive statements.
>
> I interpreted the statements as "if DeleteDate is already non-null then
> don't replicate" and "if DeleteDate becomes non-null then delete from
> subscriber". In particular, a row with DeleteDate non-null might have
> some other column changed (in which case it shouldn't be replicated), or
> might have DeleteDate set back to null (in which case it should be
> replicated).
Navigation:
[Reply to this message]
|