I will not bother pasting code because that does not seem to be the issue. I have SQL in an internal PROC to grab details about a vendor record. When I run the code in the program, it codes not find the values SQLSTATE 02000. When I run the SQL from the command line while in debug for the same session (read:library list), the SQL works. Go figure!!! Have you all seen anything like this? Sigh. I do not have enough hair let for "pulling my hair out" problems like this.
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
Page 1 / 1
I will not bother pasting code because that does not seem to be the issue. I have SQL in an internal PROC to grab details about a vendor record. When I run the code in the program, it codes not find the values SQLSTATE 02000. When I run the SQL from the command line while in debug for the same session (read:library list), the SQL works. Go figure!!! Have you all seen anything like this? Sigh. I do not have enough hair let for "pulling my hair out" problems like this.
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
Oh, BTW, it works in environment B but not A where I was testing. Gotta love this stuff. :)
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
Thank you for your enquiry.
I'm not seeing any Rocket Aldon related question. Perhaps you posted this in the wrong forum.
"SQLState 02000 No row was found for FETCH, UPDATE, or DELETE"
The most likely reason for this error is environmental: i.e. Wrong Library List (*LIBL) or Table does not have the expected data or the data is no longer available (already deleted).
Regards
------------------------------
Jay Mikaiel
Senior Technical Support Engineer
Rocket Software
UK
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.