I'm sorry if this was answered before - I did not find it...
We've been testing replication for a future implementation.
There is a publisher and a subscriber (there will be a couple more in the future), both running SQLServer 2000. The data in question is only changed at the publisher.
We're using transactional replication, pushing the subscription.
I'll refer to the problematic tables..
We have a table with Systems (BOSystems), one with Stands (Empr) and another that relates the two (Stands2Systems).
All data to this particular subscriber is filtered by Stand.ID=10
No problems were detected untill the creation of a system. I added the record on the BOSystems table,
and then the matching one in the Stands2Systems (with the EmprID=10, to meet the criteria).
After that I altered the System record...
Next time the agent had a "20598 - The row was not found at the Subscriber when applying the replicated command" error, referring to the new record in the BOSystems table.
I'm assuming that record was never sent to the subscriber because when it was inserted it did not meet the filter requirements, since it wasn't in the Stands2Systems table. And when I changed it afterwards that change was replicated, but the target row didn't exist on the subscriber...
Is my assumption correct? If so, is there a way to force the System record to be sent to the subscriber when it becomes related to the stand?
I reinitialized the subscription and it ran smoothly, with the system I had just added being included as expected.
Thanks in advance!
Claudia