SQL/R ODBC driver A.02.40 ----------------------------------------------------------------- Please refer to the README file, available in the server file set for a description of the SQLR/R ODBC A.02.40 release. Please Note: * The A.02.40 client can not be used with any older server. If you encounter a "Protocol failure" during connect, the client and server revisions are not compatible. * Please read the following section about known problems and troubleshooting. ----------------------------------------------------------------- Known Problems and Troubleshooting ----------------------------------------------------------------- Reporting Problems ------------------ If you have EMail, please send your problem report to our support EMail address "support@marxmeier.com" (without the enclosing quotes). If you don't have access to EMail, please send problem reports by Fax to +49 202 2431420. When reporting a problem, please include the contents of the SQL view of your query whenever possible. This makes it more likely for us to reproduce the problem or "guess" the cause of the problem. If you encounter a problem while programming MS Access or VBA macros, please include them with your problem report along with as much information as possible. If you set the Debug configuration item in the section [Debug] to 1, the code location which issued an error is identified with the error message. Please include this information in your problem report when possible. You can also put additional information on our ftp server in the /incoming directory if they are too large or inconvenient to include them in your mail. Please include the filename in your problem report. Intermittend crashes/hangs in MS Query on Windows 16 bit -------------------------------------------------------- The SQL/R ODBC client uses the CTL3DV2.DLL to achieve a 3D appearance. However some versions of the CTL3DV2.DLL can cause either a system hang or a GPF in MS Query. The CTL3DV2.DLL included with the SQL/R ODBC client has been tested, but since a lot of programs tend to install their own version, you may still be hit by this problem. You can either re-install the CTL3DV2.DLL included with SQL/R ODBC or disable the use of the CTL3DV2.DLL in the sqlrodbc.ini configuration file. Not enough Memory during install or driver setup (WIN16) -------------------------------------------------------- The SQL/R driver requires a WINSOCK.DLL. If it is either not installed or cannot be located by Windows, the setup program (and when loading the setup dialog, the ODBC Driver Manager too) complains it is unable to load the SQL/R ODBC DLL due to memory problems. This condition is _NOT_ fatal. When the setup program tries to load the SQL/R driver, all files already have been installed succesfully. Just make sure you have a working WINSOCK.DLL and open the ODBC Driver Manager in the control panel. MS Access 7.0 is incompatible with Windows NT 4.0 ------------------------------------------------- At least the current version of MS Access 7.0 does not work properly with Windows NT 4.0. For exmaple the "Form" and "Report" Wizards create zero-sized fields. This is not a problem of SQL/R ODBC. MS Access 7.0 / Outer Joins --------------------------- MS Access 7.0 does _not_ use an underlying ODBC driver to realize an outer join. Instead it will transfer all tables separately from the server and does the join itself. It tries to overcome a limit of the ODBC 2.0 standard which limits outer joins to two tables. While this seems smart at a first glance, just try to imagine what happens if it tries this with a 100 MB table. Problems with MS Access 2000 ---------------------------- When you try to open a linked SQL/R table, you may receive an error message like "Microsoft Access cannot open this table in datasheet view". This is caused by a bug in the MS Data Access Components before version MDAC 2.1.2.4202.3 (GA). To solve this problem, the most recent MS Data Access Components must be installed from http://www.microsoft.com/data/ - please make sure to download the most recent release of the Generally Available (GA) version of the MS Data Access Components (MDAC) in your language (the version should be at least 2.1.2.4202.3). The A.02.32 client fixes a problem concerning TIMESTAMP parameters, they were not recognized in previous releases. Since MS Access 2000 seems to be the first application which uses the TIMESTAMP data type this did not cause any problems before.