🚀 go-pugleaf

IBReplicator will log an insert and and update in this example. It will 
perform an insert and an update, however the update will basically do 
nothing if they run at the same time as when it does the insert it takes the 
data on the record as of the start of replication.

eg.
DB1 > Add record
ID = 1 Name = James Birthday = ???
DB1 > Update to
ID = 1 Name = James Birthday = 24/04/77

Replicate now
DB2 will take the insert from DB1 and add
ID = 1 Name = James Birthday = 24/04/77
and will then see an update (and do nothing)
ID = 1 Name = James Birthday = 24/04/77

If you want to get really clever you can use Stored procedures and replicate 
to the stored procedure to make sure certain events and actions have 
happened after an update. (not sure of your specifics, but this is possible)

Hope that helps
Steve

"Massimiliano Trezzi" <support_leavethis_@intesanet.com> wrote in message 
news:42885d2c@newsgroups.borland.com...
>
> Hi,
>
> Maybe I need to use IBReplicator, but before trying it, I have to know a 
> thing about how it works.
> I need an update strategy like this: every modification to the source 
> database must have the same modification (Insert-Update-Delete) in the 
> target.
> If the source insert a record and then it updates it (maybe in the same 
> transaction), it this must be handled with an Insert and an Update on the 
> target.
> I know that this is not very optimized, but in the context I need 
> replication it must works in this way.
> Can it work like this?
>
>
> Thank you in advance,
>    Massimiliano Trezzi
>
>
>
>
>