When I have run across this problem it has been
where I have encountered a character that was
not a valid one for the character set the
database was originally defined with: An extended
ascii character in an ascii database for example.
Which is often _invisible_ when I display it
but not whjen I look at it's actual value(s).

Steve Fields

--- In IBObjects@yahoogroups.com, Joe Martinez <joe@j...> wrote:
>
> > >
> > >Yes. These are the values for the primary key. The name of the
primary
> > >key column is PRODBARCODE and is of type VARCHAR(25).
> > >
> > >
> > >What I mean is, for example, if instead of setting the SQL to:
> > >Select * from products where PRODBARCODE = 'KBSolidRED'
> > >
> > >I instead set it to:
> > >Select * from products where PRODBARCODE = 'KBSolidWH'
> > >
> > >The first case generates an AV. The second case doesn't generate
an AV,
> > >but displays the record correctly.
> >
> >What KeyLinks are set for the TIBOTable?
>
> PRODBARCODE
>
>
> >Did this ever work before?
>
> Yes. In fact, it works fine in most cases. I've only received the
> complaint of this happening from a few of my customers. I had one
of them
> send me their database, so was able to reproduce it.
>
> -Joe