Bernie, Then Razzak's solution is the best one.
You can probably tell what table your JunkTable is an image of. At some point, you added or changed a column in a table, and R:BASE got confused or interrupted before the whole process was done. The JunkTable is probably the "before" table, but the constraints pointing to it didn't get completely removed and replaced by the time the interruption occurred. Find the properly named version of the table, and figure out what it's primary key is. Then look for the other tables that should have FK's pointing to that PK. Chances are very high that one of those other tables is still referencing JunkTable or the funny-named version, or in fact may have an FK referencing no table at all. Bill. On Thu, Oct 28, 2010 at 10:06 PM, Bernard Lis <[email protected]> wrote: > Thanks Bill, I did this and got: > <WARNING> No rows exist or satisfy the specified clause. (2059) > > ----- Original Message ----- > *From:* Bill Downall <[email protected]> > *To:* RBASE-L Mailing List <[email protected]> > *Sent:* Thursday, October 28, 2010 9:55 PM > *Subject:* [RBASE-L] - Re: Finding constraints > > Bernie, > > But put a space between "18" and "as" in this line. > > Bill > > On Thu, Oct 28, 2010 at 9:27 PM, Bill Downall < > [email protected]> wrote: > >> fk2.sys_column_name=18as `FK Column` + >> > >
