Bde Error 12289 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 Home Support Offerings Submit Case Resources Downloads Contact Us Printer-friendly Support KB » InterBase » Drivers » BDE Show All [All] Handling the "Capability not supported" error Abstract: Handling the "Capability not supported" error 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 then the BDE will look at this parameter in the driver definition. Alias definitions can be created by using TDatabase component, by using the DbiOpenDatabase() and DbiAddAlias() BDE API calls, and by using the BDE Administrator (formerly the BDE Configuration) utility. Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved. Site Map Installation & Registration Annual Agreements Single Incident Supported Versions Installation & Registration Product Support Single
Oracle 8i, running under Sun Microsystems Solaris 8. Parallel to the DB upgrade, we had to upgrade our http://support.codegear.com/article/34890 Oracle clients to v8.1.7.1 and the BDE 5.01 + SQL Links to work with Oracle 8 client. Now, I have this 3-tier Delphi5 application which shows the message code http://www.delphigroups.info/2/f1/228321.html 12289 - "Capability not supported" whenever I try to ApplyUpdates to my ClientDataSet object. What can be the cause to that problem? Thanks in advance. Mauro Other Threads 1. Capability Not supported.....why not? 2. 12289: Merkmal nicht verfügbar 3. problem with Batchmove bde error 12289 4. Problem - Getting Capability not supported 5. Capability Not Supported Error 6. capability not supported 7. Error: 'Capability not supported' 8. capability not supported 9. Capability Not Supported, Delphi 4, Oracle 8 10. "capability not supported" w/MSAccess DB
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 recordWhat http://www.delphifaq.com/faq/delphi/database/f1.shtml 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 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 Additional information bde error 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 Access/Security Violation 42 bde error 12289 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 Open 527 020F Do not open the