|  | February 2002
| More Information About The Magic Gateway for ODBC Version 8.20-8.20 |
| Dear Developer, We are happy to introduce The Magic Gateway for ODBC Version 8.20-8.20. This version is a bug-fix release for Magic Versions 8.20 and above. We hope you will find working with our product enjoyable and fruitful. |
| Changes in the current release: 8-20 QCR 753785 - Magic crashes intermittently when updating\inserting a date field due to a lost of range in the task. 8-19 QCR 441174 - Trying to delete a record when one of it's columns is defined as integer logical with a size of 2 fails with the error statement "Record has been lost". QCR 980623 - When issuing a link outer join without selecting all the columns, Magic fails, in some cases, to retrieve the proper records from the DB. QCR 755114 - When performing get definition on an Access table the SQL_CHAR columns are retrieved with a length twice their real size. New support - The ODBC gateway will support tables with up to 512 columns. 8-18 QCR 434841 – Adding support for locating on blank strings for ODBC drivers that support VARCHAR datatype only (and not CHAR datatype). 8-17 Support for MGTIME SQL Type - Once using this SQL Type, Magic will map Magic String Time to ODBC SQL_TIME datatype. The value ‘MGTIME’ has to be specified in the SQL Type property of the column. This is the only keyword that is not a real database datatype. The datatype created in the database will be SQL_TIME. This will be exactly the same as specifying SQL_TIME , or not specifying any SQL Type at all. 2. Support for Magic logical fields of Integer Logical length 2. The default mapping of Integer Logical fields with storage 1 or 2 is still to SQL_BIT datatype. In order to overwrite Integer Logical fields mapping with length 2, specify SQL_INTEGER in the SQL Type property of the column. 8-16 QCR 474201 - Magic crashes when updating\deleting a field with null value in a specific case. QCR 753225 - Running a Task with two Link Left Outer joins and no main table fields selected causes Magic to crash. First Link is on a constant and the second link is on the key field of the first linked table. 8.15 The MCF file can be saved in an ODBC data source. QCR 769474 - memory is not released when running a Direct SQL batch task in a loop. QCR 984507 - When getting definition from ODBC directed to ACUodbc (cobol), just the first segment in the first key is appear correctly, others gets number of fields that do not exist. QCR 777012 - When working with a Blob image in Pervasive ODBC and trying to save the record, the error message:"Invalid precision value" appears. QCR 436622 - A Table in ODBC Access brings error upon Get Definition and upon update due to type Currency in the database. 8.14 QCR 194058 - Using DBRECS function with blanks in the table name's parameter crashes Magic with 'File Manager Fatal Error' message. 8.13 QCR 384411 - Extended fetch is disabled when adding the flag SQL_EXTENDED_FETCH=N in the database information field of the Database properties tab. QCR 194058: Magic crashes with 'File Manager Fatal Error' if DBRECS() function is having spaces in its table name parameter. |
| Thank you, The Magic Version 8 Team |