Error Code Bde
Contents |
Tweet » Help List of BDE error codes Error code - hex (decimal) Error description $0000 (0) Successful completion $0021 (33) System Error $0022 (34) Object of Interest Not Found $0023 (35) Physical Data bde error 8458 Corruption $0024 (36) I/O Related Error $0025 (37) Resource or Limit Error $0026 bde error 9473 (38) Data Integrity Violation $0027 (39) Invalid Request $0028 (40) Lock Violation $0029 (41) Access/Security Violation $002A (42) Invalid bde error $210d Context $002B (43) OS Error $002C (44) Network Error $002D (45) Optional Parameter $002E (46) Query Processor $002F (47) Version Mismatch $0030 (48) Capability Not Supported $0031 (49) System Configuration Error bde error 13059 $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) 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
Bde Error 8712
(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/BLOB file $2305 (8965) Corrupt index $2306 (8966) Corrupt lock file $2307 (8967) Corrupt family file $2308 (8968) Corrupt or missing .VAL file $2309 (8969) Foreign index file format $2401 (9217) Read failure $2402 (9218) Write failure $2403 (9219) Cannot access directory $2404 (9220) File Delete operation failed $2405 (9221) Cannot access file $2406 (9222) Access to table disabled because of previous error $2501 (9473) Insufficient memory for this operation $2502 (9474)
its meaning ? Thanks in advance Craig Kinsma Delphi Developer Wed, 18 Jun 1902 08:00:00 GMT Re:Delphi database (BDE) error code Hi Sobari, Enjoy: This lists all the errors that can be returned by
Bde Error $000f
the BDE. This information is derived from IDAPI.H (C++) or BDE.INT (C++ Builder and Delphi). bde error $2501 You also wish to look at the following document(s) for addition information on specific errors: TI2733 - Troubleshooting IDAPI Error Messages TI2814 - blitz brigade error code 1-success Handling EDBEngineError Exceptions TI3160 - BDE and Database Desktop Locking Protocol Note: You can use DbiGetErrorString() to retrieve the error string for any error. System Related (Fatal Error) 8449 : $2101 : Cannot open a system http://delphidabbler.com/tips/211 file. 8450 : $2102 : I/O error on a system file. 8451 : $2103 : Data structure corruption. 8452 : $2104 : Cannot find Engine configuration file. 8453 : $2105 : Cannot write to Engine configuration file. 8454 : $2106 : Cannot initialize with different configuration file. 8455 : $2107 : System has been illegally re-entered. 8456 : $2108 : Cannot locate IDAPI32 .DLL. 8457 : http://www.delphigroups.info/2/b0/39532.html $2109 : Cannot load IDAPI32 .DLL. 8458 : $210A : Cannot load an IDAPI service library. 8459 : $210B : Cannot create or open temporary file. 8460 : $210C : Trying to load multiple IDAPIxx.DLL 8461 : $210D : Shared Memory Conflict Object of Interest not Found 8705 : $2201 : At beginning of table. 8706 : $2202 : At end of table. 8707 : $2203 : Record moved because key value changed. 8708 : $2204 : Record/Key deleted. 8709 : $2205 : No current record. 8710 : $2206 : Could not find record. 8711 : $2207 : End of BLOB. 8712 : $2208 : Could not find object. 8713 : $2209 : Could not find family member. 8714 : $220A : BLOB file is missing. 8715 : $220B : Could not find language driver. Physical Data Corruption 8961 : $2301 : Corrupt table/index header. 8962 : $2302 : Corrupt file - other than header. 8963 : $2303 : Corrupt Memo/BLOB file. 8965 : $2305 : Corrupt index. 8966 : $2306 : Corrupt lock file. 8967 : $2307 : Corrupt family file. 8968 : $2308 : Corrupt or missing .VAL file. 8969 : $2309 : Foreign index file forma
the new machine, the following error message appeared: "Unable to merge changes into BDE config file" Now, when I try to run dBASE, the following http://www.dbase.com/Knowledgebase/faq/bde_cfg_error.asp error message appears "Wrong version on IDAPI32.DLL" A: Note that all of these answers were originally designed for a deployed Visual dBASE application, but may easily solve other problems with BDE Installations ... ============================================================ The first possible solution comes from InstallShield, but was written for the use of InstallShield Express. It may help, and may not. The information comes from their website, article Q100670: "This message bde error may be displayed due to one of several reasons The target machine's pre-existing IDAPI32.CFG file is read-only or is inaccessable (in use, perhaps). InstallShield Express finds the existing IDAPI configuration by reading the location from the HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine\ key in the registry (in the CONFIGFILE01 value). If the .CFG file is not in this location, you will need to update the users' registry to point to the error code bde correct location, or delete this registry key. If the .CFG file is in this location, shut down any application that may be using the BDE, and/or check to see if the .CFG is set to read-only (if so, change that quick!). The target machine's BDE Administrator is running during installation. If this is the case, the BDE will not allow the .CFG which is open to be modified. (Shut down the BDE Administrator and try the installation again.) The IDAPI configuration file on the target machine is corrupt. To test this, launch the machine's BDE Administrator and open the configuration file from the path shown in the registry (see first point above). Try using the program's "Merge Configuration ..." option (under the "Object" menu) to merge another configuration file with the IDAPI file (try the IDAPI32.CNF located in the InstallShield Express "Redist" subdirectory). Also try saving the machine's IDAPI32.CFG as a new temporary name and open the IDAPI.CNF in the InstallShield Express "Redist" subdirectory, save as "IDAPI32.CFG", and re-run the installation. You can see if this works with a "Clean" configuration file. The only drawback to doing the above is that any prior settings may be lost -- however, if the .CFG
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 22:26:51 GMT by s_wx1094 (squid/3.5.20)