Migrating from Progress SQL-89 Connectivity to SQL-92 Connectivity Migrating from Progress SQL-89 connectivity (Progress 7.x through 9.1x) to SQL-92 connectivity (Progress 9.1x through OpenEdge 10.x and beyond) presents many challenges. This is especially the case as more and more organizations move to Progress OpenEdge 10.x and newer. These challenges apply to all data access mechanisms -- ODBC, JDBC, OLE DB, ADO.NET, etc.With proper planning, most known challenges are quickly and easily resolvable. (Some challenges do require more time and effort than others!)This guide advises you of some of the hurdles ahead and shows you how to properly plan for them and troubleshoot them.Challenges Data access challenges presented by Progress SQL-92 connectivity include -- All Shared Memory connectivity is replaced with TCP (i.e., "Sockets") connectivity. All SQL-92 connections require a username and password (though the password may be blank). This username may be an entry in the Progress _User table or in sysprogress, or, if no database users have been set up, the username of the operating system user that created (or now owns) the database file, e.g., isports.db. Unqualified identifiers (e.g., tablename vs owner.tablename) may result in errors unless/until extra steps are taken. Tableview configuration is no longer available. This impacts -- Distributed Databases -- An ODBC DSN targeting Progress 9 through OpenEdge 10.1A can only work with one Progress database (one .db file) at a time. USE dbname and similar functionality can still change the target from one database to another within that connection, but JOINs across Progress "distributed databases" (multiple .db files) are not possible over a single ODBC connection. Note Progress has re-enabled JOINs over Distributed Databases as of OpenEdge 10.1B. As of this writing, we are testing this functionality in our drivers, and will update documentation as soon as this is fully supported. Array Fields -- Array data cannot be accessed using SQL-89 syntax (i.e., field@1, field@2, etc.). New SQL-92 syntax is available, but is more complex to work with. Progress trigger support is not available through SQL-92 connections. Progress Data Dictionary (schema) definitions of data fields with content exceeding their specified length must be adjusted. Prerequisites To move forward with SQL-92 connectivity, you need to do the following on the Progress host: Ensure your target Progress instance is running in Sockets Mode. Optinally, configure a supplementary Progress Broker to accept SQL-based (as opposed to 4GL/ABL-based) connections. Ensure your target Progress instance is running in "SQL" or "Mixed" (SQL + 4GL/ABL) Mode. ("Mixed" mode is only available with Progress 9.1x.) If you are using our Single-Tier "Lite" Drivers, Progress® SQL-92 Client Access must be installed and functional on the same machine as our driver. Choosing between SQL-89 and SQL-92 Connectivity We support both SQL-89 and SQL-92 connections wherever possible.If you are a veteran OpenLink user, you may be familiar with our SQL-89 drivers, which have letter-version-specific branding in their product names, e.g., "Multi-Threaded Database Agent for Progress 8.2A" and "Multi-Threaded ODBC Driver for Progress 9.1D."Our SQL-92 drivers are only major-version-specific, e.g., "Multi-Threaded Database Agent for Progress 9 (SQL-92)" and "Multi-Threaded ODBC Driver for Progress 10 (SQL-92)."