I have seen this behaviour when the index is corrupt (assumed as
I got the correct answer following a backup & restore)

>From: "csswa" <csswa@...>
>WHAT WORKED...
>
>I changed the line above from
>
>WHERE RDB$INDEX_NAME =
>
>to
>
>WHERE RDB$INDEX_NAME IN
>
>and suddenly the loop produces the correct values for var_pkname.
>Now, whenever var_tablename gets a new value, var_pkname is updated
>accordingly with the table's primary key column name. Weird, huh.
>This seems to badly violate singleton logic, and for it to work the
>IN has to be producing just one value in the set.
>
>Okay, well that's it for now. I have totally twisted my brain on
>this one and lost about 6 hours. I'm happy to have got it working
>but the logic still escapes me and that's a continuing worry.
>
>Any further thoughts on this appreciated. I have a couple of ideas
>about how this might be a bug (handling of variables within an SP)
>but I can't think of a way to test/reproduce it by other means.
>However, as always I expect that there is a logical explanation and
>that the server is just doing what I told it to do.
>
>Regards,
>Andrew Ferguson
>
>
>

_________________________________________________________________
Join the world�s largest e-mail service with MSN Hotmail.
http://www.hotmail.com