Did the record exist at the time the error was reported? I have seen cases
before where the Parent record is physically sent to the remote *after* the
Child record. This would explain why the error was legitimately reported but
when you look at the database later the Parent record now exists.
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/cx.stm?starturl=casemessage.ssc?CASETYPE=B
ug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
Post by Tasha TravisI'm getting this error message sporadically when my remote sites are
replicating to my central server. The odd thing is the record that is the
primary key value does exist!
I'm at a lost...Does any have any idea, why this may be happening?
Thanks
Tasha