View Incident Report

Serious

Reported By: Charles Bainbridge
Reported On: 9/17/2018
For: Version 2.28 Build 7

# 4692 ODBC Driver Not Handling Encoded Dates Properly When Used with MS Query

We're migrating users to our EDB-based system from DBISAM people are now hitting problems with the queries generated by MS Query.

The SQL generated by MS Query against an EDB database generates error #700, whereas, the same query executed against a DBISAM DSN works and returns a result set.

SELECT Orderh.REF, Orderh.ORDDATE
FROM "_DEFAULT".Orderh Orderh
WHERE (Orderh.ORDDATE>{d '2018-01-01'})
ORDER BY Orderh.REF

Comments

The issue wasn't specific to MS Query, rather that is just one prominent client application that uses the special ODBC-encoded date format.

Resolution

Fixed Problem on 9/20/2018 in version 2.29 build 1

Products Affected

ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap