Stephen:
Earlier this week I spent a great deal of time "fixing" all of the FK rows that did not correspond to PKs that I had established. If I had known that the FK creation process would ignore noncompliant rows, I definitely would have run the suggested work-around prior to establishing the FKs. This is one of the existing RBase traps for the unwary and I, for one, appreciate that you have made it known to the RBase developer community. RSyntax does not provide any reference to this issue. Don't you think it should? Thanks Tony Anthony J. Schmidt, JD President The Computery Ltd. One East Main Street Bay Shore, NY 11706 631-665-8100 Voice 631-969-5988 FAX http://www.computeryltd.com |---------+----------------------------> | | owner-rbase-l@son| | | etmail.com | | | | | | 04/07/2002 01:29 | | | PM | | | Please respond to| | | rbase-l | | | | |---------+----------------------------> >---------------------------------------------------------------------------------------------------------------------------------------------| | | | To: [EMAIL PROTECTED] | | cc: (bcc: Anthony Schmidt/BayShore/SGU_LN) | | Subject: RE: An old bug? | >---------------------------------------------------------------------------------------------------------------------------------------------| The solution is to run a statement before applying the foreign key that checks existing data, then correct the data. EDIT * FROM <table> WHERE <fkColumn> NOT IN (SELECT <pkColumn> FROM <pkTable>) "Stephen Markson" <[EMAIL PROTECTED]> wrote: >I reported in May 2001 that the foreign key building process did not >check the references to the PK. At the time Razzak replied that it would >be fixed in the next release. Indeed, the "Bug Fix" list at >http://www.rbase2000.com/rbw65pp/MoreBugFixes.htm includes "PK to FK >References (#1630)". (Should that be "FK to PK..."?). However, RBW 1.851 >RT03 still does not check the references. It builds the index and gives >no error message if there is no matching data in the PK table. > >Regards, > >Stephen Markson >ForenSys The Forensic Systems Group >www.ForensicSystemsGroup.com >416 482 2140 > >================================================ >TO SEE MESSAGE POSTING GUIDELINES: >Send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: INTRO rbase-l >================================================ >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: UNSUBSCRIBE rbase-l >================================================ >TO SEARCH ARCHIVES: >http://www.mail-archive.com/rbase-l%40sonetmail.com/ > __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
