Skip to end of metadataGo to start of metadata![Odbc Odbc](https://offlinefreewarefiles.com/wp-content/uploads/2020/09/driver-talent-free-scaled.jpg)
- Ms Odbc
- Free Odbc Driver For Mac Numbers 7
- Free Odbc Driver For Mac Numbers 2016
- Free Odbc Driver For Mac Numbers Download
2018-3-26 Microsoft ODBC Driver 13.1 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, Analytics Platform System, Azure SQL Database and Azure SQL Data Warehouse. The most important attribute to iODBC for each datasource is the Driver attribute. This must point to the shared library for the ODBC driver associated with the data source. As example, the OpenLink ODBC drivers have a number of attributes which can be set for a data source. Here is a description (with ODBC connect string tags between parenthesis).
These instructions are for the Hive ODBC driver available in Hive for HiveServer1.
There is no ODBC driver available for HiveServer2 as part of Apache Hive. There are third party ODBC drivers available from different vendors, and most of them seem to be free.
There is no ODBC driver available for HiveServer2 as part of Apache Hive. There are third party ODBC drivers available from different vendors, and most of them seem to be free.
Free JDBC-ODBC Bridge v.1.0 FreeJOB is a free, open-source alternative to Sun's JDBC- ODBC Bridge. FreeJOB allows Java applications to query and access databases via the native Windows ODBC. The Desktop Edition of the driver is intended for standalone desktop applications such as MS Excel and FileMaker Pro. To use the driver with a server-based application (such as FileMaker Server or Apache), you will need a Server Edition license. See here for more information about licenses. Note: each Mac where the driver is installed counts as. Hi, I am developing a Excel VBA application using a.xlsx workbook as database. This database is addressed by SQL queries through an ActualTechnologies Access ODBC driver. This worked very well, given.
HiveServer was removed from Hive releases starting with Hive 1.0.0. See HIVE-6977. Please switch over to HiveServer2.
Introduction
Sony vaio pcg 6n1l drivers for mac. The Hive ODBC Driver is a software library that implements the Open Database Connectivity (ODBC) API standard for the Hive database management system, enabling ODBC compliant applications to interact seamlessly (ideally) with Hive through a standard interface. This driver will NOT be built as a part of the typical Hive build process and will need to be compiled and built separately according to the instructions below.
Suggested Reading
This guide assumes you are already familiar with the following:
![Odbc Odbc](https://offlinefreewarefiles.com/wp-content/uploads/2020/09/driver-talent-free-scaled.jpg)
Software Requirements
The following software components are needed for the successful compilation and operation of the Hive ODBC driver:
- Hive Server – a service through which clients may remotely issue Hive commands and requests. The Hive ODBC driver depends on Hive Server to perform the core set of database interactions. Hive Server is built as part of the Hive build process. More information regarding Hive Server usage can be found here.
- Apache Thrift – a scalable cross-language software framework that enables the Hive ODBC driver (specifically the Hive client) to communicate with the Hive Server. See this link for the details on Thrift Installation. The Hive ODBC driver was developed with Thrift trunk version r790732, but the latest revision should also be fine. Make sure you note the Thrift install path during the Thrift build process as this information will be needed during the Hive client build process. The Thrift install path will be referred to as THRIFT_HOME.
Driver Architecture
Internally, the Hive ODBC Driver contains two separate components: Hive client, and the unixODBC API wrapper.
- Hive client – provides a set of C-compatible library functions to interact with Hive Server in a pattern similar to those dictated by the ODBC specification. However, Hive client was designed to be independent of unixODBC or any ODBC specific headers, allowing it to be used in any number of generic cases beyond ODBC.
- unixODBC API wrapper – provides a layer on top of Hive client that directly implements the ODBC API standard. The unixODBC API wrapper will be compiled into a shared object library, which will be the final form of the Hive ODBC driver. The wrapper files will remain a file attachment on the associated JIRA until it can be checked into the unixODBC code repository: HIVE-187, HIVE-1101.
Building and Setting Up ODBC Components
NOTE: Hive client needs to be built and installed before the unixODBC API wrapper can compile successfully.
Hive Client Build/Setup
In order to build and install the Hive client:
- Checkout and setup the latest version of Apache Hive from the Subversion or Git source code repository. For more details, see Getting Started with Hive. From this point onwards, the path to the Hive root directory will be referred to as HIVE_SRC_ROOT.Using a tarball source releaseIf you are compiling against source code contained in the tarball release package then HIVE_SRC_ROOT refers to the 'src' subdirectory.The ODBC driver is broken on trunk!Currently the C++ Thrift client library that the ODBC driver depends on will not build on trunk. This issue is being tracked in HIVE-4433. If you are using trunk prior to release 0.12 check the status of this ticket before proceeding. Also see HIVE-4492.
- Build the Hive client by running the following command from HIVE_SRC_ROOT. This will compile and copy the libraries and header files to
HIVE_SRC_ROOT/build/odbc/
. Please keep in mind that all paths should be fully specified (no relative paths). If you encounter an 'undefined reference to vtables
' error, make sure that you have specified the absolute path for thrift.home.MVN:
You can optionally force Hive client to compile into a non-native bit architecture by specifying the additional parameter (assuming you have the proper compilation libraries):
- You can verify the entire Hive compilation by running the Hive test suite from HIVE_SRC_ROOT. Specifying the argument '-Dthrift.home=<THRIFT_HOME>' will enable the tests for the Hive client. If you do NOT specify thrift.home, the Hive client tests will not be run and will just return successful.MVN:You can specifically execute the Hive client tests by running the above command from
HIVE_SRC_ROOT/odbc/
. NOTE: Hive client tests require that a local Hive Server be operating on port 10000. - To install the Hive client libraries onto your machine, run the following command from
HIVE_SRC_ROOT/odbc/
. NOTE: The install path defaults to/usr/local
. While there is no current way to change this default directory from the ant build process, a manual install may be performed by skipping the command below and copying out the contents ofHIVE_SRC_ROOT/build/odbc/lib
andHIVE_SRC_ROOT/build/odbc/include
into their local file system counterparts.NOTE: The compiled static library, libhiveclient.a, requires linking with stdc++ as well as thrift libraries to function properly.
NOTE: Currently, there is no way to specify non-system library and header directories to the unixODBC build process. Thus, the Hive client libraries and headers MUST be installed to a default system location in order for the unixODBC build process to detect these files. This issue may be remedied in the future.
unixODBC API Wrapper Build/Setup
After you have built and installed the Hive client, you can now install the unixODBC API wrapper:
Ms Odbc
- In the unixODBC root directory, run the following command:If you encounter the the errors: '
redefinition of 'struct _hist_entry'
' or 'previous declaration of 'add_history' was here
' then re-execute the configure with the following command:To force the compilation of the unixODBC API wrapper into a non-native bit architecture, modify the CC and CXX environment variables to include the appropriate flags. For example: - Argus dcf license key. Compile the unixODBC API wrapper with the following:If you want to completely install unixODBC and all related drivers, run the following from the unixODBC root directory:If your system complains about
undefined symbols
during unixODBC testing (such as withisql
orodbcinst
) after installation, try runningldconfig
to update your dynamic linker's runtime libraries.
If you only want to obtain the Hive ODBC driver shared object library: - After compilation, the driver will be located at
<unixODBC_BUILD_DIR>/Drivers/hive/.libs/libodbchive.so.1.0.0
.
This may be copied to any other location as desired. Keep in mind that the Hive ODBC driver has a dependency on the Hive client shared object library:libhiveclient.so
andlibthrift.so.0
.
You can manually install the unixODBC API wrapper by doing the following:
Connecting the Driver to a Driver Manager
This portion assumes that you have already built and installed both the Hive client and the unixODBC API wrapper shared libraries on the current machine. To connect the Hive ODBC driver to a previously installed Driver Manager (such as the one provided by unixODBC or a separate application):
- Locate the odbc.ini file associated with the Driver Manager (DM).
- If you are installing the driver on the system DM, then you can run the following command to print the locations of DM configuration files.
- If you are installing the driver on an application DM, then you have to help yourself on this one . Hint: try looking in the installation directory of your application.
- Keep in mind that an application's DM can exist simultaneously with the system DM and will likely use its own configuration files, such as odbc.ini.
- Also, note that some applications do not have their own DMs and simply use the system DM.
- Add the following section to the DM's corresponding odbc.ini:
Testing with ISQL
Once you have installed the necessary Hive ODBC libraries and added a Hive entry in your system's default odbc.ini, you will be able to interactively test the driver with isql:
If your system does not have isql, you can obtain it by installing the entirety of unixODBC. If you encounter an error saying that the shared libraries cannot be opened by isql, use the
ldd
tool to ensure that all dynamic library dependencies are resolved and use the file
tool to ensure that isql and all necessary libraries are compiled into the same architecture (32 or 64 bit).Build libodbchive.so for 3rd Party Driver Manager
If you want to build libodbchive.so for other Driver Manager (for example, MicroStrategy uses DataDirect ODBC libraries which contains its own Driver Manager), you need to configure and build libodbchive.so against that Driver Manager (libodbc.so and libodbcinst.so).
If you have the 3rd party Driver Manager installed, the easiest way to do that is to find the installation directory containing libodbc.so and libodbcinst.so, and set that directory to LD_LIBRARY_PATH. Then you need to run configure and make for the Hive ODBC driver. After you get the libodbchive.so, make sure the 3rd party application can access the dynamic library libodbchive.so, libthrift.so and libhiveclient.so (through LD_LIBRARY_PATH or ldconfig).
If you build libodbchive.so for the 3rd party Driver Manager, isql may not work with the same set of .so files. So you may need to compile a different libodbchive.so for each Driver Manager.
Troubleshooting
- Hive client build process
- 'libthrift.a: could not read symbols: Bad value' or 'relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object'?
- Try recompiling your Apache Thrift libraries with the -fPIC option for your C++ compiler
- 'undefined reference to vtable' ?
- Make sure that your Apache Thrift libraries are being included from the proper Thrift directory and that it has the same architecture (32 or 64 bit) as the Hive client.
- Also, check to make sure you are providing a fully qualified path for the thrift.home parameter.
- In general,
ldd
,file
, andnm
are essential unix tools for debugging problems with shared object libraries. If you don't know what they are, useman
to get more details.
- 'libthrift.a: could not read symbols: Bad value' or 'relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object'?
Current Status
- Comments: Please keep in mind that this is still an initial version and is still very rough around the edges. However, it provides basic ODBC 3.51 API support for connecting, executing queries, fetching, etc. This driver has been successfully tested on 32-bit and 64-bit linux machines with iSQL. It has also been tested with partial success on enterprise applications such as MicroStrategy. Due to licensing reasons, the unixODBC API wrapper files will be uploaded as a separate JIRA attachment that will not be part of this code repository.
- Limitations:
- Only support for Linux operating systems
- No support for Unicode
- No support for asynchronous execution of queries
- Does not support pattern matching for functions such as SQLColumns and SQLTables; requires exact matches.
- Hive Server is currently not thread safe (see JIRA HIVE-80: https://issues.apache.org/jira/browse/HIVE-80). This will prevent the driver from safely making multiple connections to the same Hive Server. We need to resolve this issue to allow the driver to operate properly.
- Hive Server's getSchema() function seems to have trouble with certain types of queries (such as 'SELECT * .' or 'EXPLAIN'), and so the Hive ODBC driver sometimes has difficulties with these queries as well.
- ODBC API Function Support (does anyone know how to remove the linking from the function names?):
SQLAllocConnect
supportedSQLAllocEnv
supportedSQLAllocHandle
supportedSQLAllocStmt
supportedSQLBindCol
supportedSQLBindParameter
NOT supportedSQLCancel
NOT supportedSQLColAttribute
supportedSQLColumns
supportedSQLConnect
supportedSQLDescribeCol
supported Fallout new vegas eve mod.SQLDescribeParam
NOT supportedSQLDisconnect
supportedSQLDriverConnect
supportedSQLError
supportedSQLExecDirect
supportedSQLExecute
supportedSQLExtendedFetch
NOT supportedSQLFetch
supportedSQLFetchScroll
NOT supportedSQLFreeConnect
supportedSQLFreeEnv
supportedSQLFreeHandle
supportedSQLFreeStmt
supportedSQLGetConnectAttr
NOT supportedSQLGetData
supported (however, SQLSTATE not returning values)SQLGetDiagField
NOT supportedSQLGetDiagRec
supportedSQLGetInfo
partially supported; (to get MSTR v9 running)SQLMoreResults
NOT supportedSQLNumParams
NOT supportedSQLNumResultCols
supportedSQLParamOptions
NOT supportedSQLPrepare
supported; but does not permit parameter markersSQLRowCount
NOT supportedSQLSetConnectAttr
NOT supportedSQLSetConnectOption
NOT supportedEgyptian revival font free download.SQLSetEnvAttr
Limited supportSQLSetStmtAttr
NOT supportedSQLSetStmtOption
NOT supportedSQLTables
supportedSQLTransact
NOT supported
To an ADO or RDS programmer, an ideal world would be one in which every data source exposes an OLE DB interface, so that ADO could call directly into the data source. Although increasingly more database vendors are implementing OLE DB interfaces, some data sources are not yet exposed this way. However, most DBMS systems in use today can be accessed through ODBC.
ODBC drivers are available for every major DBMS in use today, including Microsoft SQL Server, Microsoft Access (Microsoft Jet database engine), and Microsoft FoxPro, in addition to non-Microsoft database products such as Oracle.
The Microsoft ODBC Provider, however, allows ADO to connect to any ODBC data source. The provider is free-threaded and Unicode enabled.
The provider supports transactions, although different DBMS engines offer different types of transaction support. For example, Microsoft Access supports nested transactions up to five levels deep.
This is the default provider for ADO, and all provider-dependent ADO properties and methods are supported.
Connection String Parameters
To connect to this provider, set the Provider= argument of the ConnectionString property to:
Reading the Provider property will return this string as well.
Typical Connection String
A typical connection string for this provider is:
The string consists of these keywords:
Keyword | Description |
---|---|
Provider | Specifies the OLE DB provider for ODBC. |
DSN | Specifies the data source name. |
UID | Specifies the user name. |
PWD | Specifies the user password. |
URL | Specifies the URL of a file or directory published in a Web folder. |
Because this is the default provider for ADO, if you omit the Provider= parameter from the connection string, ADO will try to establish a connection to this provider.
Note
If you are connecting to a data source provider that supports Windows authentication, you should specify Trusted_Connection=yes or Integrated Security = SSPI instead of user ID and password information in the connection string.
Indesign cs5.5 mac torrent. The provider does not support any specific connection parameters in addition to those defined by ADO. However, the provider will pass any non-ADO connection parameters to the ODBC driver manager.
Because you can omit the Provider parameter, you can therefore compose an ADO connection string that is identical to an ODBC connection string for the same data source. Use the same parameter names (DRIVER=, DATABASE=, DSN=, and so on), values, and syntax as you would when composing an ODBC connection string. You can connect with or without a predefined data source name (DSN) or FileDSN.
Syntax with a DSN or FileDSN:
Syntax without a DSN (DSN-less connection):
Remarks
If you use a DSN or FileDSN, it must be defined through the ODBC Data Source Administrator in the Windows Control Panel. In Microsoft Windows 2000, the ODBC Administrator is located under Administrative Tools. In earlier versions of Windows, the ODBC Administrator icon is named 32-bit ODBC or just ODBC.
As an alternative to setting a DSN, you can specify the ODBC driver (DRIVER=), such as 'SQL Server;' the server name (SERVER=); and the database name (DATABASE=).
You can also specify a user account name (UID=), and the password for the user account (PWD=) in the ODBC-specific parameters or in the standard ADO-defined user and password parameters.
Although a DSN definition already specifies a database, you can specify adatabase parameter in addition to a DSN to connect to a different database. It is a good idea to always include thedatabase parameter when you use a DSN. This will ensure that you connect to the correct database if another user changed the default database parameter since you last checked the DSN definition.
Provider-Specific Connection Properties
The OLE DB provider for ODBC adds several properties to the Properties collection of the Connection object. The following table lists these properties with the corresponding OLE DB property name in parentheses.
Property Name | Description |
---|---|
Accessible Procedures (KAGPROP_ACCESSIBLEPROCEDURES) | Indicates whether the user has access to stored procedures. |
Accessible Tables (KAGPROP_ACCESSIBLETABLES) | Indicates whether the user has permission to execute SELECT statements against the database tables. |
Active Statements (KAGPROP_ACTIVESTATEMENTS) | Indicates the number of handles an ODBC driver can support on a connection. |
Driver Name (KAGPROP_DRIVERNAME) | Indicates the file name of the ODBC driver. |
Driver ODBC Version (KAGPROP_DRIVERODBCVER) | Indicates the version of ODBC that this driver supports. |
File Usage (KAGPROP_FILEUSAGE) | Indicates how the driver treats a file in a data source; as a table or as a catalog. |
Like Escape Clause (KAGPROP_LIKEESCAPECLAUSE) | Indicates whether the driver supports the definition and use of an escape character for the percent character (%) and underline character (_) in the LIKE predicate of a WHERE clause. |
Max Columns in Group By (KAGPROP_MAXCOLUMNSINGROUPBY) | Indicates the maximum number of columns that can be listed in the GROUP BY clause of a SELECT statement. |
Max Columns in Index (KAGPROP_MAXCOLUMNSININDEX) | Indicates the maximum number of columns that can be included in an index. |
Max Columns in Order By (KAGPROP_MAXCOLUMNSINORDERBY) | Indicates the maximum number of columns that can be listed in the ORDER BY clause of a SELECT statement. |
Max Columns in Select (KAGPROP_MAXCOLUMNSINSELECT) | Indicates the maximum number of columns that can be listed in the SELECT portion of a SELECT statement. |
Max Columns in Table (KAGPROP_MAXCOLUMNSINTABLE) | Indicates the maximum number of columns allowed in a table. |
Numeric Functions (KAGPROP_NUMERICFUNCTIONS) | Indicates which numeric functions are supported by the ODBC driver. For a listing of function names and the associated values used in this bitmask, see Appendix E: Scalar Functions, in the ODBC documentation. |
Outer Join Capabilities (KAGPROP_OJCAPABILITY) | Indicates the types of OUTER JOINs supported by the provider. |
Outer Joins (KAGPROP_OUTERJOINS) | Indicates whether the provider supports OUTER JOINs. |
Special Characters (KAGPROP_SPECIALCHARACTERS) | Indicates which characters have special meaning for the ODBC driver. |
Stored Procedures (KAGPROP_PROCEDURES) | Indicates whether stored procedures are available for use with this ODBC driver. |
String Functions (KAGPROP_STRINGFUNCTIONS) | Indicates which string functions are supported by the ODBC driver. For a listing of function names and the associated values used in this bitmask, see Appendix E: Scalar Functions, in the ODBC documentation. |
System Functions (KAGPROP_SYSTEMFUNCTIONS) | Indicates which system functions are supported by the ODBC driver. For a listing of function names and the associated values used in this bitmask, see Appendix E: Scalar Functions, in the ODBC documentation. |
Time/Date Functions (KAGPROP_TIMEDATEFUNCTIONS) | Indicates which time and date functions are supported by the ODBC driver. For a listing of function names and the associated values used in this bitmask, see Appendix E: Scalar Functions, in the ODBC documentation. |
SQL Grammar Support (KAGPROP_ODBCSQLCONFORMANCE) | Indicates the SQL grammar that the ODBC driver supports. |
Provider-Specific Recordset and Command Properties
The OLE DB provider for ODBC adds several properties to the Properties collection of the Recordset and Command objects. The following table lists these properties with the corresponding OLE DB property name in parentheses.
Property Name | Description |
---|---|
Query Based Updates/Deletes/Inserts (KAGPROP_QUERYBASEDUPDATES) | Indicates whether updates, deletions, and insertions can be performed by using SQL queries. |
ODBC Concurrency Type (KAGPROP_CONCURRENCY) | Indicates the method used to reduce potential problems caused by two users trying to access the same data from the data source simultaneously. |
BLOB accessibility on Forward-Only cursor (KAGPROP_BLOBSONFOCURSOR) | Indicates whether BLOB Fields can be accessed when using a forward-only cursor. |
Include SQL_FLOAT, SQL_DOUBLE, and SQL_REAL in QBU WHERE clauses (KAGPROP_INCLUDENONEXACT) | Indicates whether SQL_FLOAT, SQL_DOUBLE, and SQL_REAL values can be included in a QBU WHERE clause. |
Position on the last row after insert (KAGPROP_POSITIONONNEWROW) | Indicates that after a new record has been inserted in a table, the last row in the table will be come the current row. |
IRowsetChangeExtInfo (KAGPROP_IROWSETCHANGEEXTINFO) | Indicates whether the IRowsetChange interface provides extended information support. |
ODBC Cursor Type (KAGPROP_CURSOR) | Indicates the type of cursor used by the Recordset. |
Generate a Rowset that can be marshaled (KAGPROP_MARSHALLABLE) | Indicates that the ODBC driver generates a recordset that can be marshaled |
Command Text
How you use the Command object largely depends on the data source, and what type of query or command statement it will accept.
ODBC provides a specific syntax for calling stored procedures. For the CommandText property of a Command object, the CommandText argument to the Execute method on a Connection object, or the Source argument to the Open method on a Recordset object, passes in a string with this syntax:
Each ? references an object in the Parameters collection. The first ? references Parameters(0), the next ? references Parameters(1), and so on.
The parameter references are optional and depend on the structure of the stored procedure. If you want to call a stored procedure that defines no parameters, your string would look like the following:
If you have two query parameters, your string would resemble the following:
If the stored procedure will return a value, the return value is treated as another parameter. If you have no query parameters but you do have a return value, your string would resemble the following:
Finally, if you have a return value and two query parameters, your string would resemble the following:
Recordset Behavior
The following tables list the standard ADO methods and properties available on a Recordset object opened with this provider.
Free Odbc Driver For Mac Numbers 7
For more detailed information about Recordset behavior for your provider configuration, run the Supports method and enumerate the Properties collection of the Recordset to determine whether provider-specific dynamic properties are present.
Availability of standard ADO Recordset properties:
Property | ForwardOnly | Dynamic | Keyset | Static |
---|---|---|---|---|
AbsolutePage | not available | not available | read/write | read/write |
AbsolutePosition | not available | not available | read/write | read/write |
ActiveConnection | read/write | read/write | read/write | read/write |
BOF | read-only | read-only | read-only | read-only |
Bookmark | not available | not available | read/write | read/write |
CacheSize | read/write | read/write | read/write | read/write |
CursorLocation | read/write | read/write | read/write | read/write |
CursorType | read/write | read/write | read/write | read/write |
EditMode | read-only | read-only | read-only | read-only |
Filter | read/write | read/write | read/write | read/write |
LockType | read/write | read/write | read/write | read/write |
MarshalOptions | read/write | read/write | read/write | read/write |
MaxRecords | read/write | read/write | read/write | read/write |
PageCount | read/write | not available | read-only | read-only |
PageSize | read/write | read/write | read/write | read/write |
RecordCount | read/write | not available | read-only | read-only |
Source | read/write | read/write | read/write | read/write |
State | read-only | read-only | read-only | read-only |
Status | read-only | read-only | read-only | read-only |
The AbsolutePosition and AbsolutePage properties are write-only when ADO is used with version 1.0 of the Microsoft OLE DB Provider for ODBC.
Availability of standard ADO Recordset methods:
Method | ForwardOnly | Dynamic | Keyset | Static |
---|---|---|---|---|
AddNew | Yes | Yes | Yes | Yes |
Cancel | Yes | Yes | Yes | Yes |
CancelBatch | Yes | Yes | Yes | Yes |
CancelUpdate | Yes | Yes | Yes | Yes |
Clone | No | No | Yes | Yes |
Close | Yes | Yes | Yes | Yes |
Delete | Yes | Yes | Yes | Yes |
GetRows | Yes | Yes | Yes | Yes |
Move | Yes | Yes | Yes | Yes |
MoveFirst | Yes | Yes | Yes | Yes |
MoveLast | No | Yes | Yes | Yes |
MoveNext | Yes | Yes | Yes | Yes |
MovePrevious | No | Yes | Yes | Yes |
NextRecordset* | Yes | Yes | Yes | Yes |
Open | Yes | Yes | Yes | Yes |
Requery | Yes | Yes | Yes | Yes |
Resync | No | No | Yes | Yes |
Supports | Yes | Yes | Yes | Yes |
Update | Yes | Yes | Yes | Yes |
UpdateBatch | Yes | Yes | Yes | Yes |
*Not supported for Microsoft Access databases.
Dynamic Properties
The Microsoft OLE DB Provider for ODBC inserts several dynamic properties into the Properties collection of the unopened Connection, Recordset, and Command objects.
Free Odbc Driver For Mac Numbers 2016
The following tables are a cross-index of the ADO and OLE DB names for each dynamic property. The OLE DB Programmer's Reference refers to an ADO property name by the term, 'Description.' You can find more information about these properties in the OLE DB Programmer's Reference. Search for the OLE DB property name in the Index or see Appendix C: OLE DB Properties.
Connection Dynamic Properties
The following properties are added to the Connection object's Properties collection.
Free Odbc Driver For Mac Numbers Download
ADO Property Name | OLE DB Property Name |
---|---|
Active Sessions | DBPROP_ACTIVESESSIONS |
Asynchable Abort | DBPROP_ASYNCTXNABORT |
Asynchable Commit | DBPROP_ASYNCTNXCOMMIT |
Autocommit Isolation Levels | DBPROP_SESS_AUTOCOMMITISOLEVELS |
Catalog Location | DBPROP_CATALOGLOCATION |
Catalog Term | DBPROP_CATALOGTERM |
Column Definition | DBPROP_COLUMNDEFINITION |
Connect Timeout | DBPROP_INIT_TIMEOUT |
Current Catalog | DBPROP_CURRENTCATALOG |
Data Source | DBPROP_INIT_DATASOURCE |
Data Source Name | DBPROP_DATASOURCENAME |
Data Source Object Threading Model | DBPROP_DSOTHREADMODEL |
DBMS Name | DBPROP_DBMSNAME |
DBMS Version | DBPROP_DBMSVER |
Extended Properties | DBPROP_INIT_PROVIDERSTRING |
GROUP BY Support | DBPROP_GROUPBY |
Heterogeneous Table Support | DBPROP_HETEROGENEOUSTABLES |
Identifier Case Sensitivity | DBPROP_IDENTIFIERCASE |
Initial Catalog | DBPROP_INIT_CATALOG |
Isolation Levels | DBPROP_SUPPORTEDTXNISOLEVELS |
Isolation Retention | DBPROP_SUPPORTEDTXNISORETAIN |
Locale Identifier | DBPROP_INIT_LCID |
Location | DBPROP_INIT_LOCATION |
Maximum Index Size | DBPROP_MAXINDEXSIZE |
Maximum Row Size | DBPROP_MAXROWSIZE |
Maximum Row Size Includes BLOB | DBPROP_MAXROWSIZEINCLUDESBLOB |
Maximum Tables in SELECT | DBPROP_MAXTABLESINSELECT |
Mode | DBPROP_INIT_MODE |
Multiple Parameter Sets | DBPROP_MULTIPLEPARAMSETS |
Multiple Results | DBPROP_MULTIPLERESULTS |
Multiple Storage Objects | DBPROP_MULTIPLESTORAGEOBJECTS |
Multi-Table Update | DBPROP_MULTITABLEUPDATE |
NULL Collation Order | DBPROP_NULLCOLLATION |
NULL Concatenation Behavior | DBPROP_CONCATNULLBEHAVIOR |
OLE DB Services | DBPROP_INIT_OLEDBSERVICES |
OLE DB Version | DBPROP_PROVIDEROLEDBVER |
OLE Object Support | DBPROP_OLEOBJECTS |
Open Rowset Support | DBPROP_OPENROWSETSUPPORT |
ORDER BY Columns in Select List | DBPROP_ORDERBYCOLUMNSINSELECT |
Output Parameter Availability | DBPROP_OUTPUTPARAMETERAVAILABILITY |
Password | DBPROP_AUTH_PASSWORD |
Pass By Ref Accessors | DBPROP_BYREFACCESSORS |
Persist Security Info | DBPROP_AUTH_PERSIST_SENSITIVE_AUTHINFO |
Persistent ID Type | DBPROP_PERSISTENTIDTYPE |
Prepare Abort Behavior | DBPROP_PREPAREABORTBEHAVIOR |
Prepare Commit Behavior | DBPROP_PREPARECOMMITBEHAVIOR |
Procedure Term | DBPROP_PROCEDURETERM |
Prompt | DBPROP_INIT_PROMPT |
Provider Friendly Name | DBPROP_PROVIDERFRIENDLYNAME |
Provider Name | DBPROP_PROVIDERFILENAME |
Provider Version | DBPROP_PROVIDERVER |
Read-Only Data Source | DBPROP_DATASOURCEREADONLY |
Rowset Conversions on Command | DBPROP_ROWSETCONVERSIONSONCOMMAND |
Schema Term | DBPROP_SCHEMATERM |
Schema Usage | DBPROP_SCHEMAUSAGE |
SQL Support | DBPROP_SQLSUPPORT |
Structured Storage | DBPROP_STRUCTUREDSTORAGE |
Subquery Support | DBPROP_SUBQUERIES |
Table Term | DBPROP_TABLETERM |
Transaction DDL | DBPROP_SUPPORTEDTXNDDL |
User ID | DBPROP_AUTH_USERID |
User Name | DBPROP_USERNAME |
Window Handle | DBPROP_INIT_HWND |
Recordset Dynamic Properties
The following properties are added to the Recordset object's Properties collection.
ADO Property Name | OLE DB Property Name |
---|---|
Access Order | DBPROP_ACCESSORDER |
Blocking Storage Objects | DBPROP_BLOCKINGSTORAGEOBJECTS |
Bookmark Type | DBPROP_BOOKMARKTYPE |
Bookmarkable | DBPROP_IROWSETLOCATE |
Change Inserted Rows | DBPROP_CHANGEINSERTEDROWS |
Column Privileges | DBPROP_COLUMNRESTRICT |
Column Set Notification | DBPROP_NOTIFYCOLUMNSET |
Delay Storage Object Updates | DBPROP_DELAYSTORAGEOBJECTS |
Fetch Backwards | DBPROP_CANFETCHBACKWARDS |
Hold Rows | DBPROP_CANHOLDROWS |
IAccessor | DBPROP_IAccessor |
IColumnsInfo | DBPROP_IColumnsInfo |
IColumnsRowset | DBPROP_IColumnsRowset |
IConnectionPointContainer | DBPROP_IConnectionPointContainer |
IConvertType | DBPROP_IConvertType |
Immobile Rows | DBPROP_IMMOBILEROWS |
IRowset | DBPROP_IRowset |
IRowsetChange | DBPROP_IRowsetChange |
IRowsetIdentity | DBPROP_IRowsetIdentity |
IRowsetInfo | DBPROP_IRowsetInfo |
IRowsetLocate | DBPROP_IRowsetLocate |
IRowsetResynch | |
IRowsetUpdate | DBPROP_IRowsetUpdate |
ISequentialStream | DBPROP_ISequentialStream |
ISupportErrorInfo | DBPROP_ISupportErrorInfo |
Literal Bookmarks | DBPROP_LITERALBOOKMARKS |
Literal Row Identity | DBPROP_LITERALIDENTITY |
Maximum Open Rows | DBPROP_MAXOPENROWS |
Maximum Pending Rows | DBPROP_MAXPENDINGROWS |
Maximum Rows | DBPROP_MAXROWS |
Notification Granularity | DBPROP_NOTIFICATIONGRANULARITY |
Notification Phases | DBPROP_NOTIFICATIONPHASES |
Objects Transacted | DBPROP_TRANSACTEDOBJECT |
Own Changes Visible | DBPROP_OWNUPDATEDELETE |
Own Inserts Visible | DBPROP_OWNINSERT |
Preserve on Abort | DBPROP_ABORTPRESERVE |
Preserve on Commit | DBPROP_COMMITPRESERVE |
Quick Restart | DBPROP_QUICKRESTART |
Reentrant Events | DBPROP_REENTRANTEVENTS |
Remove Deleted Rows | DBPROP_REMOVEDELETED |
Report Multiple Changes | DBPROP_REPORTMULTIPLECHANGES |
Return Pending Inserts | DBPROP_RETURNPENDINGINSERTS |
Row Delete Notification | DBPROP_NOTIFYROWDELETE |
Row First Change Notification | DBPROP_NOTIFYROWFIRSTCHANGE |
Row Insert Notification | DBPROP_NOTIFYROWINSERT |
Row Privileges | DBPROP_ROWRESTRICT |
Row Resynchronization Notification | DBPROP_NOTIFYROWRESYNCH |
Row Threading Model | DBPROP_ROWTHREADMODEL |
Row Undo Change Notification | DBPROP_NOTIFYROWUNDOCHANGE |
Row Undo Delete Notification | DBPROP_NOTIFYROWUNDODELETE |
Row Undo Insert Notification | DBPROP_NOTIFYROWUNDOINSERT |
Row Update Notification | DBPROP_NOTIFYROWUPDATE |
Rowset Fetch Position Change Notification | DBPROP_NOTIFYROWSETFETCHPOSISIONCHANGE |
Rowset Release Notification | DBPROP_NOTIFYROWSETRELEASE |
Scroll Backwards | DBPROP_CANSCROLLBACKWARDS |
Skip Deleted Bookmarks | DBPROP_BOOKMARKSKIPPED |
Strong Row Identity | DBPROP_STRONGITDENTITY |
Unique Rows | DBPROP_UNIQUEROWS |
Updatability | DBPROP_UPDATABILITY |
Use Bookmarks | DBPROP_BOOKMARKS |
Command Dynamic Properties
The following properties are added to the Command object's Properties collection.
ADO Property Name | OLE DB Property Name |
---|---|
Access Order | DBPROP_ACCESSORDER |
Blocking Storage Objects | DBPROP_BLOCKINGSTORAGEOBJECTS |
Bookmark Type | DBPROP_BOOKMARKTYPE |
Bookmarkable | DBPROP_IROWSETLOCATE |
Change Inserted Rows | DBPROP_CHANGEINSERTEDROWS |
Column Privileges | DBPROP_COLUMNRESTRICT |
Column Set Notification | DBPROP_NOTIFYCOLUMNSET |
Delay Storage Object Updates | DBPROP_DELAYSTORAGEOBJECTS |
Fetch Backwards | DBPROP_CANFETCHBACKWARDS |
Hold Rows | DBPROP_CANHOLDROWS |
IAccessor | DBPROP_IAccessor |
IColumnsInfo | DBPROP_IColumnsInfo |
IColumnsRowset | DBPROP_IColumnsRowset |
IConnectionPointContainer | DBPROP_IConnectionPointContainer |
IConvertType | DBPROP_IConvertType |
Immobile Rows | DBPROP_IMMOBILEROWS |
IRowset | DBPROP_IRowset |
IRowsetChange | DBPROP_IRowsetChange |
IRowsetIdentity | DBPROP_IRowsetIdentity |
IRowsetInfo | DBPROP_IRowsetInfo |
IRowsetLocate | DBPROP_IRowsetLocate |
IRowsetResynch | |
IRowsetUpdate | DBPROP_IRowsetUpdate |
ISequentialStream | DBPROP_ISequentialStream |
ISupportErrorInfo | DBPROP_ISupportErrorInfo |
Literal Bookmarks | DBPROP_LITERALBOOKMARKS |
Literal Row Identity | DBPROP_LITERALIDENTITY |
Maximum Open Rows | DBPROP_MAXOPENROWS |
Maximum Pending Rows | DBPROP_MAXPENDINGROWS |
Maximum Rows | DBPROP_MAXROWS |
Notification Granularity | DBPROP_NOTIFICATIONGRANULARITY |
Notification Phases | DBPROP_NOTIFICATIONPHASES |
Objects Transacted | DBPROP_TRANSACTEDOBJECT |
Own Changes Visible | DBPROP_OWNUPDATEDELETE |
Own Inserts Visible | DBPROP_OWNINSERT |
Preserve on Abort | DBPROP_ABORTPRESERVE |
Preserve on Commit | DBPROP_COMMITPRESERVE |
Quick Restart | DBPROP_QUICKRESTART |
Reentrant Events | DBPROP_REENTRANTEVENTS |
Remove Deleted Rows | DBPROP_REMOVEDELETED |
Report Multiple Changes | DBPROP_REPORTMULTIPLECHANGES |
Return Pending Inserts | DBPROP_RETURNPENDINGINSERTS |
Row Delete Notification | DBPROP_NOTIFYROWDELETE |
Row First Change Notification | DBPROP_NOTIFYROWFIRSTCHANGE |
Row Insert Notification | DBPROP_NOTIFYROWINSERT |
Row Privileges | DBPROP_ROWRESTRICT |
Row Resynchronization Notification | DBPROP_NOTIFYROWRESYNCH |
Row Threading Model | DBPROP_ROWTHREADMODEL |
Row Undo Change Notification | DBPROP_NOTIFYROWUNDOCHANGE |
Row Undo Delete Notification | DBPROP_NOTIFYROWUNDODELETE |
Row Undo Insert Notification | DBPROP_NOTIFYROWUNDOINSERT |
Row Update Notification | DBPROP_NOTIFYROWUPDATE |
Rowset Fetch Position Change Notification | DBPROP_NOTIFYROWSETFETCHPOSITIONCHANGE |
Rowset Release Notification | DBPROP_NOTIFYROWSETRELEASE |
Scroll Backwards | DBPROP_CANSCROLLBACKWARDS |
Skip Deleted Bookmarks | DBPROP_BOOKMARKSKIP |
Strong Row Identity | DBPROP_STRONGIDENTITY |
Updatability | DBPROP_UPDATABILITY |
Use Bookmarks | DBPROP_BOOKMARKS |
For details regarding specific implementation and functional information about the Microsoft OLE DB Provider for ODBC, see the OLE DB Programmer's Reference or visit the Data Access and Storage Developer Center Web site on MSDN.