Thanks David, This of course also works for temp tables. I am using that to determine if a temp table is there or not. If not, I use project temporary to create it. If it is there, I delete rows from it.
Bernie Lis
----- Original Message ----- From: "David M. Blocker" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[email protected]>
Sent: Friday, March 18, 2005 10:40 AM
Subject: [RBG7-L] - RE: Create Error Code Table
Claudine
Back to your original question. If tracing showed the view was NOT getting created, you could easily check for THAT in your program like this:
*(Assume view name is zTempTable) SELECT COUNT(*) INTO vIsTheViewThere IND vI1 FROM SYS_TABLES WHERE SYS_TABLE_NAME = 'zTempTable' IF vIsTheViewThere = 0 THEN -- error message that no data / no view exists! ENDIF
David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: "claudinerobbins" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Thursday, March 17, 2005 7:51 PM Subject: [RBG7-L] - RE: Create Error Code Table
andHi Javier,
I've gotten used to doing that too before and after creating temp tablesviews to suppress the error messages. But I wanted to capture it instead!I
I was looking for a system variable change that would indicate to me a
failure to create the view since I thought that it would not be created at
all... but now I know differently since Buddy's code works like a charm.
Also, the recent question posed on the list about sqlstate = HY000 still puzzles me.
Claudine :)
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Javier Valencia Sent: Thursday, March 17, 2005 4:32 PM To: RBG7-L Mailing List Subject: [RBG7-L] - RE: Create Error Code Table
Claudine:
I know that you got several ways of addressing this problem. One way I use
to find out the error code is to:
SET MESSAGES ON
SET ERROR MESSAGES ON
And then trace the code, when you get to the command in question, it will
display the error message and the error message number; then, if necessaryanduse SET ERROR MESSAGE xxxx OFF -- run your command here SET ERROR MESSAGE xxxx ON During trace, I also keep track of the error code variable as well as the sqlcode and sqlstate. Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the senderthatdelete the material from all system and destroy all copies. ======================================================
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Claudine Robbins Sent: Thursday, March 17, 2005 11:39 AM To: RBG7-L Mailing List Subject: [RBG7-L] - Create Error Code Table
Hi everyone,
I'm looking for the error code for "record not found" or something liketo trap in a form.
I tried running both David Blocker's rewrite of Oma's errorcode1.rmd file and Oma's original and I can't get either to execute without errors.
TIA, Claudine :)
