Interbase Error
code messages include the name of a database object or object type, the name is represented by a code in the Message column:
another transaction, but not yet committed. In this case, the procedure might receive an InterBase error code, isc_lock_conflict. Perhaps if the procedure retries its update, the other transaction may have rolled back its changes and released its locks. By using a WHEN GDSCODE statement, the procedure can handle lock conflict errors and retry its operation. Example: For example, if a procedure attempts to insert a duplicate value into a column defined as a PRIMARY KEY, InterBase http://docwiki.embarcadero.com/InterBase/XE7/en/InterBase_Status_Array_Error_Codes will return SQLCODE -803. This error can be handled in a procedure with the following statement: WHEN SQLCODE -803 DO BEGIN . . . For example, the following procedure, from an isql script, includes a WHEN statement to handle errors that may occur as the procedure runs. If an error occurs and SQLCODE is as expected, the http://docwiki.embarcadero.com/InterBase/XE7/en/Handling_InterBase_Error_Codes procedure continues with the new value of B. If not, the procedure cannot handle the error, and rolls back all actions of the procedure, returning the active SQLCODE. CREATE PROCEDURE NUMBERPROC (A INTEGER) RETURNS (B INTEGER) AS BEGIN B = 0; BEGIN UPDATE R SET F1 = F1 +:A; UPDATE R SET F2 = F2 * F2; UPDATE R SET F1 = F1 +:A; WHEN SQLCODE -803 DO B = 1; END EXIT; END; See Also EXCEPTION For more information about InterBase error codes and SQLCODE values, see Error Codes and Messages. Retrieved from "http://docwiki.embarcadero.com/InterBase/XE7/e/index.php?title=Handling_InterBase_Error_Codes&oldid=21366" Views Page Discussion View source History Personal tools Create account Log in Search InterBase XE7 Main Page Readme Installation, Registration, and Licensing Information Demos & Tutorials Installing InterBase ToGo Quick Start InterBase Quick Start InterBase VAR License Portal Previous Releases: InterBase XE3 Readme Tools What links here Related changes Special pages Printable version Permanent link Page information This page was last modified on 19 October 2015, at 04:40. Privacy Policy About InterBase Disclaimers
[Easysoft][Interbase]Dynamic SQL Error, SQL error code=-804 Article: 00871 Last Reviewed: 29th October 2008 http://www.easysoft.com/support/kb/kb00871.html Revision: 2 This error is often the result of mismatched InterBase client andserver versions. Search your local hard drive on the client system forgds32.dll. Make sure there is only one version and its version number(right click on the DLL in Windows Explorer and choose Properties) isidentical to the interbase error ibserver.exe version number on the server Applies To Products Easysoft ODBC-InterBase Driver Knowledge Base Feedback * Did this content help you? Yes No Maybe * Please select one option based on your first choice: I'm very satisfied I think it will help, but I haven't tried it yet interbase error It is helpful, but I need more information It is helpful, but hard to understand Seemed relevant in search results, but didn't help me The information is incorrect The page contains one or more broken links Suggest new content or let us know how we can improve this content: (* Required Fields) About Easysoft Contact Us About Us Clients Upgrade Offer Blog Careers Products ODBC Drivers JDBC Drivers Bridges and Gateways In Development Services Consultancy Training Custom Development Licensing Product Licenses Prices Support Support Home Solution Wizard Getting Started Guides User Guides Knowledge Base Search Easysoft.com Documentation Knowledge Base Popular Resources Developer Area Client Applications Legal Privacy Statement © 1993 - 2016 Easysoft Limited. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other trademarks and registered trademarks appearing on easysoft.com are the property of their respective owners.