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 necessary I use 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 sender and delete 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 like that to 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 :)
