- Publisher: VDS-ODBC ‘s Developer
- Category: Databases & Tools
- Downloads: 799
This library allows to extend possibilities of programming language Visual Dialog Script firm SADE
The library is intended for VDS version 5.x.
Key features of the library:
1. Additional controls:
• The element choice.
• Easy element of EditBox with automatic filling.
• Items pop-up menu on the Grid (right click).
• graphic elements.
• Work with any databases (including Microsoft Excel).
• To work with databases using DSN. Your program will be fully compatible with all versions of Windows.
• The use of additional controls.
• Creation of DSN. Getting the connection string.
• Working with SQL servers through DSN.
Illustrative examples will give an opportunity to quickly get acquainted with the possibilities of the library.
Caution This special edition of the library. The library will operate without registration 20 days. A reminder message about buying does not appear to make the most comfortable to do an introduction to the library.
The library has the commands and functions. A complete list of commands and functions, see the file reg_lib.txt located in the archive.
What is ODBC?
Open Database Connectivity (ODBC) is an open standard Application Programming Interface (API) for accessing a database. In 1992, Microsoft partners with Simba to build the world’s first ODBC driver; SIMBA.DLL, and standards-based data access was born. By using ODBC statements in a program, you can access files in a number of different common databases. In addition to the ODBC software, a separate module or driver is needed for each database to be accessed.
The latest version of ODBC specification is available from Microsoft‘s website.
For your convenience, you can also download a PDF version of the current ODBC 3.8 Specification.
Microsoft introduced the ODBC standard in 1992. ODBC was a standard designed to unify access to SQL databases. Following the success of ODBC, Microsoft introduced OLE DB which was to be a broader data access standard. OLE DB was a data access standard that went beyond just SQL databases and extended to any data source that could deliver data in tabular format. Microsoft’s plan was that OLE DB would supplant ODBC as the most common data access standard. More recently, Microsoft introduced the ADO data access standard. ADO was supposed to go further than OLE DB, in that ADO was more object oriented. However, even with Microsoft’s very significant attempts to replace the ODBC standard with what were felt to be “better” alternatives, ODBC has continued to be the de facto data access standard for SQL data sources. In fact, today the ODBC standard is more common than OLE DB and ADO because ODBC is widely supported (including support from Oracle and IBM) and is a cross platform data access standard. Today, the most common data access standards for SQL data sources continue to be ODBC and JDBC, and it is very likely that standards like OLE DB and ADO will fade away over time.
ODBC has become the de-facto standard for standards-based data access in both relational and non-relational database management systems (DBMS). Simba worked closely with Microsoft to co-develop the ODBC standard back in the early 90’s. The ODBC standard enables maximum interoperability thereby enabling application developers to write a single application to access data sources from different vendors. ODBC is based on the Call-Level Interface (CLI) specifications from Open Group and ISO/IEC for database APIs and uses Structured Query Language (SQL) as its database access language.
(Open DataBase Connectivity) A database programming interface from Microsoft that provides a common language for Windows applications to access databases on a network. ODBC is made up of the function calls programmers write into their applications and the ODBC drivers themselves.
For client/server database systems such as Oracle and SQL Server, the ODBC driver provides links to their database engines to access the database. For desktop database systems such as Access and FoxPro, the ODBC drivers actually manipulate the data. ODBC supports SQL and non-SQL databases. Although the application always uses SQL to communicate with ODBC, ODBC will communicate with non-SQL databases in its native language. See JDBC.
What is an ODBC Driver?
An ODBC driver uses the Open Database Connectivity (ODBC) interface by Microsoft that allows applications to access data in database management systems (DBMS) using SQL as a standard for accessing the data.
An ODBC driver uses the Open Database Connectivity (ODBC) interface by Microsoft that allows applications to access data in database management systems (DBMS) using SQL as a standard for accessing the data. ODBC permits maximum interoperability, which means a single application can access different DBMS. Application end users can then add ODBC database drivers to link the application to their choice of DBMS.
Downloading the JDBC or ODBC Driver
The JDBC or ODBC driver is used to connect to data warehouse clusters. You can download the JDBC or ODBC driver provided by GaussDB(DWS) from the management console or use the open-source JDBC or ODBC driver.
Open-Source JDBC or ODBC Driver
GaussDB(DWS) also supports open-source JDBC and ODBC drivers: PostgreSQL JDBC 9.3-1103 or later; PostgreSQL ODBC 09.01.0200 or later