ODBC/MX Driver for Windows Manual for SQL/MX Release 3.2.1 (H06.26+, J06.15+)
Table Of Contents
- HP NonStop ODBC/MX Driver for Windows
- Legal Notices
- Contents
- What’s New in This Manual
- About This Manual
- 1 ODBC/MX Client Overview
- 2 Installation of the ODBC/MX Client
- 3 Configuring Client Data Sources on Windows
- Accessing the Microsoft ODBC Data Source Administrator from a Client Workstation
- Adding New Client Data Sources
- Reconfiguring Client Data Sources
- Configuring Client Data Sources using Connection String
- Configuring Client Data Sources for Update Operations
- Configuring Driver for IPV6
- Removing Client Data Sources
- Tracing Client Data Sources
- 4 Module File Caching (MFC)
- 5 ODBC/MX Conformance
- ODBC API Functions
- SQL Conformance Level
- SQL Scalar Functions
- ODBC Data Types
- Unsigned Data Types
- Partial Date/Time Values
- SQL/MP Data Types and ODBC/MX Equivalents
- Microsoft Escape Clauses
- Stored Procedures
- Transactions and Cursor Behavior with Multiple Statements
- Timestamp Values with Fraction
- SQL Interval Insertion Property
- SQL Datetime Retrieval Property
- 6 ODBC/MX Messages
- Glossary
- Index
ODBC/MX Client Overview
HP NonStop ODBC/MX Driver for Windows—691126-002
1-12
Limitations of ODBC/MX Driver
The precision of the NUMERIC data type is extended up to 128 digits for signed
and unsigned values.
Limitations of ODBC/MX Driver
The system running an R 3.x version of Windows ODBC/MX Driver does not connect
to a NonStop system running an R 2.x version of ODBC/MX server objects.
When you try to connect an R 3.x version of Windows ODBC/MX Driver to an R 2.x
version of ODBC/MX server objects, the behavior is unpredictable.