Discussion:
SQL statement failed: (-194) No primary key value for foreign key
(too old to reply)
Tasha Travis
2004-05-14 14:18:22 UTC
Permalink
I'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
Robert Waywell
2004-05-14 15:50:00 UTC
Permalink
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 Travis
I'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
unknown
2004-05-26 19:15:00 UTC
Permalink
That means you miss some information in the
table you are referencing from the replicated table.

say you have a emplyee in IS department
but in you department table you do not have IS entry.

add the referneced record in the primary tableor
check you publication articles.

Tom
Post by Tasha Travis
I'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
Loading...