Bde Error Codes
Contents |
Tweet » Help List of BDE error codes Error code - hex (decimal) Error description $0000 (0) Successful completion $0021 (33) System bde error 8458 Error $0022 (34) Object of Interest Not Found $0023 (35)
Bde Error 9473
Physical Data Corruption $0024 (36) I/O Related Error $0025 (37) Resource or Limit Error $0026 (38)
Bde Error $210d
Data Integrity Violation $0027 (39) Invalid Request $0028 (40) Lock Violation $0029 (41) Access/Security Violation $002A (42) Invalid Context $002B (43) OS Error $002C (44)
Bde Error 13059
Network Error $002D (45) Optional Parameter $002E (46) Query Processor $002F (47) Version Mismatch $0030 (48) Capability Not Supported $0031 (49) System Configuration Error $0032 (50) Warning $0033 (51) Miscellaneous $0034 (52) Compatibility Error $003E (62) Driver Specific Error $003F (63) Internal Symbol $2101 (8449) Cannot open a system file $2102 (8450) bde error 8712 I/O error on a system file $2103 (8451) Data structure corruption $2104 (8452) Cannot find Engine configuration file $2105 (8453) Cannot write to Engine configuration file $2106 (8454) Cannot initialize with different configuration file $2107 (8455) System has been illegally re-entered $2108 (8456) Cannot locate IDAPI32 .DLL $2109 (8457) Cannot load IDAPI32 .DLL $210A (8458) Cannot load an IDAPI service library $210B (8459) Cannot create or open temporary file $2201 (8705) At beginning of table $2202 (8706) At end of table $2203 (8707) Record moved because key value changed $2204 (8708) Record/Key deleted $2205 (8709) No current record $2206 (8710) Could not find record $2207 (8711) End of BLOB $2208 (8712) Could not find object $2209 (8713) Could not find family member $220A (8714) BLOB file is missing $220B (8715) Could not find language driver $2301 (8961) Corrupt table/index header $2302 (8962) Corrupt file - other than header $2303 (8963) Corrupt Memo/BL
Swedish Traditional Chinese Turkish | Location All Other RegionsASEANAustralia/New ZealandBeneluxD-A-CHGreater ChinaLatin AmericaNordicTaiwanUK and IrelandUS and CaribbeanCountriesBrazilCanadaFranceIndiaItalyJapanKorea (South)Russian FederationSpain Embarcadero Home Watch, Follow, & bde error $000f Connect with Us Share This Communities Articles Blogs Resources Downloads bde error $2501 Help Submit Translation Printer-friendly EDN » Delphi » Database » Database Engines Show All [All] Handling BDE bde error 15879 Engine Errors By: Borland Staff Abstract: Some guidelines to handling BDE Engine errors from an InterBase perspective Problem: A Delphi or C++ Builder generated application produces http://delphidabbler.com/tips/211 a BDE Engine exception. Solution: An exception was produced in the Delphi generated application due to an error from the RDBMS server (i.e InterBase), the BDE or an ODBC driver. Using the Borland BDE Configuration Utility (BDECFG.EXE, or BDEADMIN.EXE) to examine the SQLQRYMODE property of the InterBase or Visigneic ODBC alias being used in http://edn.embarcadero.com/article/25188 the application. If the setting is or set to LOCAL change the setting to SERVER. Save the changes and exit the utility. If the application is using a TDatabase component, bring the application up in Delphi and left double-click the mouse on the TDatabase component to bring up the Database Login dialog. Change the SQLQRYMODE property in the parameters list box to SERVER, if the property is present. Save and do a Build All. At this point exiting the Delphi IDE and starting it again may be required so that the new changes in the BDE aliases will be re-read and accounted for. SQLQRYMODE Settings ======================================== : The BDE sends the SQL query string to the RDBMS server or the ODBC data source and if an error is returned the BDE will then parse the string itself and will send the parsed string (or strings) to the server. LOCAL: The BDE will parse the strings and send the parsed stri
Swedish Traditional Chinese Turkish | Location All Other RegionsASEANAustralia/New ZealandBeneluxD-A-CHGreater ChinaLatin AmericaNordicTaiwanUK and IrelandUS and CaribbeanCountriesBrazilCanadaFranceIndiaItalyJapanKorea (South)Russian http://support.codegear.com/article/35865 FederationSpain Embarcadero Home Home Support Offerings Submit Case http://forums.devart.com/viewtopic.php?t=22132 Resources Downloads Contact Us Printer-friendly Support KB » C++Builder » Errors Show All [All] "Could not initialize BDE" error when trying to start Database Desktop Abstract: "Could not initialize BDE" error when trying to start Database Desktop "Could bde error not initialize BDE" error when trying to start Database Desktop Product Name:��C++Builder� Product Version:��All� Product Component:��Database Desktop,�BDE (Borland Database Engine)� Platform/OS Version:� All Description: When I try to start Database Desktop, I get a "Could not initialize BDE" error, after which Database Desktop closes. I am also bde error codes unable to start BDE Administrator -- there are no error messages; it simply does not start when double-clicked. In addition, attempts to use the BDE from within the C++Builder IDE are met with a "An error occurred while attempting to initialize the Borland Database Engine (error $2108)" failure. Answer/Solution: This behavior strongly suggests a problem with your BDE path, which is stored in the following part of the Registry: ���� HKEY_LOCAL_MACHINE | SOFTWARE | Borland | Database Engine In that Registry key, the value CONFIGFILE01 needs to point to your idapi32.cfg file, and the value DLLPath needs to point to the directory where your idapi32.dll resides. If you have installed C++Builder and the BDE to the default directories, then the data for CONFIGFILE01 should be: ���� C:\Program Files\Common Files\Borland Shared\BDE\IDAPI32.CFG And the data for DLLPath should be: ���� C:\Program Files
Page 1 of 1 How to replace BDE error codes? by lior » Mon 26 Sep 2011 14:59 Hello, How would you replace these BDE error codes? 1) procedure UpdateError1(Sender: TObject; DataSet: TCustomClientDataSet; E: EUpdateError; UpdateKind: TUpdateKind; var Response: TResolverResponse); Begin If (UpdateKind=ukInsert)And(E.ErrorCode=9733) Then Response:=rrIgnore; //9733=Master record missing End; 2) If E is EDBEngineError Then If (EDBEngineError(E).Errors[0].ErrorCode = 9729) Then // Key Violation 3) If (E is EDBEngineError) Then If (EDBEngineError(E).Errors[0].ErrorCode = ERRBASE_OTHER + ERRCODE_UNKNOWNSQL) Then //13056 + 3 = 13059 lior Posts: 27Joined: Mon 01 Aug 2011 07:11 Top by AlexP » Tue 27 Sep 2011 09:34 Hello, You can process these errors in the onUpdateError event of the TOraTable and TOraQuery components as in TDataSetProvider. AlexP Devart Team Posts: 5429Joined: Tue 10 Aug 2010 11:35 Top by lior » Tue 27 Sep 2011 10:08 I was referring to the BDE error code. Is it the same as ODAC error code ? If EOraError(E).ErrorCode= number Then … For example some BDE error codes I check: 9733 Master record missing 9729 Key Violation 13056 + 3 = 13059 ERRBASE_OTHER + ERRCODE_UNKNOWNSQL lior Posts: 27Joined: Mon 01 Aug 2011 07:11 Top by AlexP » Tue 27 Sep 2011 15:37 Hello, BDE and ODAC codes do not match, since ODAC returns an Oracle ORA-XXXXX error code in EOraError(E).ErrorCode, while BDE returns its own error codes. AlexP Devart Team Posts: 5429Joined: Tue 10 Aug 2010 11:35 Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject AscendingDescending Post a reply 4 posts • Page 1 of 1 Return to Oracle Data Access Components Jump to: Select a forum ------------------ General Forums Announcements Database Tools dbForge for MySQL dbForge for Oracle dbForge for PostgreSQL dbForge for SQL Server ADO.NET Data Providers Entity Framework support LinqConnect (LINQ to SQL support) dotConnect for Oracle dotConnect for MySQL dotConnect for PostgreSQL dotConnect for SQLite dotConnect for DB2 dotConnect for SQL Server dotConnect for Cloud Applications dotConnect Universal Entity Developer Delphi Data Access Components EntityDAC Universal Data Access Components Oracle Data Access Components SQL Server Data Access Components MySQL Data Access Components InterBase Data Access Components PostgreSQL Data Access Components SQLite Data Access Components VirtualDAC dbExpress Drivers dbExpress driver