Subject Re: ISC_ERROR 335544652 multiple rows in singleton select
Author w1n9man
--- In IBObjects@yahoogroups.com, Lester Caine <lester@l...> wrote:
> w1n9man wrote:
>
> > -- STOP PRESS -----
> > I was just checking something using IBO Console and guess what ?
> > ISC_ERROR 335544652 from IBO Console !!
>
> That sounds like a good starting point. What were you checking?
> This problem normally happens when you try and link fields that are not
> 'unique' and so I suspect you have two entries that are the same ID
> number. Triggers and links in IBO will then complain when you try and
> use a query that needs one record, but is seeing to two.
>
> A quick fix in FB1.5 is to 'SELECT FIRST 1', but the real problem is
> probably in how you are populating the data, and needs a 'UNIQUE' index
> or even a 'PRIMARY KEY' on the field you are trying to link to.
>
> --
> Lester Caine
> -----------------------------
> L.S.Caine Electronic Services

Lester,

I was checking the WORKING table on update trigger. WORKING is a temp
table with 4 fields and has the UID field set up as a primary key. I
was trying to add a time to the finish field to check that the on
update trigger would fire. After the trigger has fired the record is
deleted (by another trigger on USERS Table) so at any given time there
should only be one refernce to a UID in the table. I have tested the
constraints for uniqueness on the UID field and they work.

The table is set up like this:

UID Integer NOT NULL PRIMARY KEY
START TIME NOT NULL
FINISH TIME
ONDATE DATE NOT NULL

I am at my wits end on this and I can honestly say that I have never
had so much trouble updating one value in a table.

Cheers

Trevor