Re: CDR27 warning message in a transaction for a 2 way replication table

Madison Pruet wrote: > Could we get the actual error message that they are seeing. I don't > know what CDR27 is. ahhh yes - shame on me. It's error number 27 (apparently) which in the appendix A of my manual, is reserved for future use; although it is named CRD_EREPLSYN - if that's the error number they mean. Basically, the code deletes a row with same primary key, and then inserts it again (doesn't update like it *should* but what can you do?), and when defined in a 2-way replicant, it yields this mysterious error. Which we'll be looking at shortly... Version numbers are probably a good idea too :-/