Database Engine Error Capability Not Supported
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, & Connect with Us Share This Communities Articles Blogs Resources Downloads Help Submit Translation Printer-friendly EDN » Delphi » Database » Database Engines Show All [All] Handling the "Capability not supported" error By: Borland Staff Abstract: An application written using the BDE, Delphi, or C++ Builder may return an error "Capability not supported." Problem: An application written using the BDE, Delphi, or C++ Builder may return an error "Capability not supported." Solution: This error is returned by the BDE when the BDE parses an SQL string to be sent to a server and the syntax of the string is not supported by the BDE. See below for more information on how the BDE sends pass through SQL strings to DBMS servers and ODBC data sources. The BDE, and Delphi and C++ Builder applications that use data-aware components send SQL strings to DBMS servers and ODBC data sources depending on the setting of the SQLQRYMODE parameters. The settings of the SQLQRYMODE parameter are listed in the BDE Administrator Help (formerly known as the BDE Configuration Help) file, and are paraphrased below: - The SQL string is sent to the server or ODBC data source first. If an error is returned the string is then parsed and ran by the BDE. SERVER - The SQL string is sent to the server or ODBC data source, if an error is returned then the error is placed on the BDE error stack and the appropriate BDE error is returned. LOCAL - The SQL string is parsed and ran by the BDE. When the BDE parses and runs the SQL string due to the SQLQRYMODE being set to blank or LOCAL, if the SQL string to be parsed is not supported by the BDE the error "Capability not supported" is returned. The SQLQRYMODE parameter is found in both BDE alias definitions and in BDE driver definitions. The BDE will look for this parameter first in the alias definition, if it is not found or the entry not a recognized value or is corrupted
2005 Posts: 78 BDE Errors In Pathloss 4.0, the following are common BDE (Borland Database Engine) errors with instructions on how to fix them. BDE Error - Operation not applicable There are two possible causes:There are old *.lck files in the shared network directory. The .NET file is corrupt. To fix either, make sure all users, including yourself, are out of The database and Paradox. In Windows Explorer, browse to the shared network directory.Open the directory and check for the two files 'Paradox.lck' and 'Pdoxusrs.lck'. If either or both are present, delete them. Open the directory and check for the file 'Pdoxusrs.net'. Delete it. If http://edn.embarcadero.com/article/25183 you get a message "access is denied", have all database users restart their pc's then try deleting the file above again, if it is still present. NOTE: The 'Pdoxusrs.net' file will recreate itself when the first user logs back in. It is normal for this file to be present even when no user is in the database. During BDE Installation, the Error Message "Merging the Configuration File has Failed" Occurs Summary During BDE http://www.pathloss.com/forums/showthread.php?t=457 installation, InstallShield Express displays the error message "Merging the configuration file has failed". Discussion InstallShield Express includes with your BDE setup a configuration file called Idapi32.cnf. (For a 16-bit setup, this file is named Idapi.cnf.) During installation, InstallShield Express copies this file to a temporary location, and then adds to it the settings you chose in the BDE Alias dialogs. If there exists no BDE on the target system, then InstallShield Express simply saves the Idapi32.cnf file to the default BDE directory as Idapi32.cfg. However, if the target machine already has BDE on it (and so has a preexisting Idapi32.cfg file), InstallShield Express then calls the BDE Merge function to merge the Idapi32.cnf file with the existing Idapi32.cfg file, thereby adding your setup's BDE aliases and settings to those already on the target system. There are several possible reasons why the message "Merging the configuration file has failed" will be displayed during BDE setup: The target machine's preexisting Idapi32.cfg file is set to read-only or is in any other way inaccessible. This will cause BDE's Merge function to fail. InstallShield Express finds the existing IDAPI configuration file by reading its current location from the CONFIGFILE01 value data under the HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine key in the target machine's registry (32-bit) or from the [IDAPI] section of the system's Win
message)Physical Data Corruption (BDE error message)I/O Related Error (BDE error message)Object of Interest not FoundCouldn't perform the edit because another user changed the http://www.delphifaq.com/faq/delphi/database/f1.shtml recordWhat to do about $210A error message This article has not been rated yet. After reading, feel free to leave comments and rate it. Some of those errors http://support.flexquarters.com/esupport/index.php?/Knowledgebase/Article/View/2403/0/qodbc-desktop-error-capability-not-supported-in-delphi-with-qodbc represent classes of errors - they are linked e.g. error 34. To obtain more information about BDE Errors at runtime, please read Obtaining more information about BDE Errors database engine Additional information about BDE error codes are available in file \DELPHI\DOC\DBIERRS.INT. 0 0000 Successful completion. 33 0021 System Error 34 0022 Object of Interest Not Found 35 0023 Physical Data Corruption 36 0024 I/O Related Error 37 0025 Resource or Limit Error 38 0026 Data Integrity Violation 39 0027 Invalid Request 40 0028 Lock Violation 41 0029 database engine error Access/Security Violation 42 002A Invalid Context 43 002B OS Error 44 002C Network Error 45 002D Optional Parameter 46 002E Query Processor 47 002F Version Mismatch 48 0030 Capability Not Supported 49 0031 System Configuration Error 50 0032 Warning 51 0033 Miscellaneous 52 0034 Compatibility Error 62 003E Driver Specific Error 63 003F Internal Symbol 256 0100 KEYVIOL 257 0101 PROBLEMS 258 0102 CHANGED 512 0200 Production Index file missing, corrupt or cannot interpret index key 513 0201 Open Read Only 514 0202 Open the table in read only mode 515 0203 Open and Detach 516 0204 Open the table and detach the Production Index file 517 0205 Fail Open 518 0206 Do not open the table 519 0207 Convert Non-dBase Index 520 0208 Convert production index to dBase format 521 0209 BLOB file not found 522 020A Open without blob file 523 020B Open the table without the blob file 524 020C Empty all blob fields 525 020D Reinitialize BLOB file and LOSE all blobs 526 020E Fail Op
(41)QXL Support (6)QODBC (6)QODBC Online (8)QODBC POS SEARCH Knowledgebase [QODBC-Desktop] Error: 'Capability not supported' in Delphi with QODBC Posted by Juliet on 27 December 2010 08:03 AM Error: 'Capability not supported' in Delphi with QODBC Problem Description I am using Delphi to access the QODBC driver. Simple test program. Has a query, data source and grid on a form. Database Name in the Query properties is set to Quickbooks Data. Some things work fine, some do not. For example... 'Select * from Transaction' works just fine, but 'select * from Account' returns the error: 'Capability not supported. [QODBC] Driver not capable' But when I run the VB Demo and put the same sql statement in, it returns data just fine. I installed QB, then the QODBC drivers, then had to do a repair on QB. Below are some error information from the qodbctra.txt file: ISAMGetData 0x005A3268 [ISAM] 0x09141968 [Account] COLUMN: 7 (Pass Through) OFFSET: 0 RawXML: FALSE ForceUnoptimized: FALSE DoNotMoveToCache: FALSE UpdateOptimized: FALSE SQL_C_SHORT -13108 MAX LENGTH: 2 LENGTH RETURNED: 2 ERR_NOTCAPABLE S1C00 IM001 [QODBC] Driver not capable ISAMGetErrorMessage 0x005A3268 [ISAM] S1C00 IM001 [QODBC] Driver not capable ISAMCloseTable 0x005A3268 [ISAM] 0x09141968 [Account] NO_ISAM_ERR 00000 00000 After further checking, the VENDER table has columns that are Boolean/Bit/YesNo fields (IsActive) and 'select * from Vender' gives the same results. Solution The issue is that the driver is having problems with the data type SQL_C_SHORT. I am not sure why Delphi is wanting Booleans returned as SQL_C_SHORT. Considering how many copies of QODBC are out there, this does not come up. Try the query below: SELECT ListID, {fn CONVERT("IsActive", SQL_INTEGER)} AS "IsActive" FROM Customer The select statement did work, and Delphi does want the Booleans as SQL_C_SHORT. The problem was with the BDE. Note: If testing with a simple BDE TQuery with the database name set to 'QUICKBOOKS DATA'. Along with the error as above, you could always get a pop-up for the login info. So an option is to switch to using an ADOConnection and an ADOQuery with the connection string set to: Provider=MSDASQL.1;Persist Security Info=False;Data Source=QuickBooks Data; That could get rid of the pop up AND seems to handle the Boolean issue just fine. (403 vote(s)) Helpful Not helpful Comments (0) Post a new commentReply to comment Full Name: Email: Comments: CAPTCHA Verification Please enter the text you see in the image into the textbox below (we use this to prevent au