On 8/30/06, Don Parris <[EMAIL PROTECTED]> wrote:
On 8/30/06, Frank Schönheit - Sun Microsystems Germany
<[EMAIL PROTECTED]> wrote:
>
> Hi Don,
>
> > When I try to establish the relationship as
> > tlb_A.field1 = tbl_B.field1
> >
> > I get the following:
> >
> > SQL Status: 23000
> > Error code: -177
> >
> > Integrity constraint violation - no parent 133, table: tbl_Survey2006
> in
> > statement [ALTER TABLE "tbl_Survey2006" ADD FOREIGN KEY ("biz_id")
> > REFERENCES "tbl_BizContact" ("biz_id")]
>
> I assume that in "tbl_Survey2006", you have a record with "biz_id"
> beeing 133, but "tbl_BizContact" is missing a record with "biz_id" being
> 133. Thus, a relationship cannot be established, since for this
> particular survey record, there's no contact record which it refers to.
Aha! That's what the '133' refers to. I'll look into that. Thanks for
the input.
Well, I found the problem in my Calc sheet, but created a new problem. My
Calc sheet had a few empty rows, where I had intended to add some new
records, but forgot to delete the empty rows when I did the copy/paste
operation. I fixed that, and when I try the copy/paste operation, I create
the table with no errors. However, attempting to open the table causes OOo
to crash. And yes, it's repeatable.
I use Ubuntu Dapper on a Dell Latitued with 256MB RAM. I'm going to attempt
it again at work on a more robust workstation. I'll see what happens there.
