![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Connectivity » View Thread |
Messages 1 to 3 of 3 total |
![]() |
Mon, Sep 17 2018 11:52 AM | Permanent Link |
Charles Bainbridge | Is there any solution for users of MS Query, beyond editing the generated SQL, for querying date-type columns in an EDB database? 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:- SELECT Orderh.REF, Orderh.ORDDATE FROM "_DEFAULT".Orderh Orderh WHERE (Orderh.ORDDATE>{d '2018-01-01'}) ORDER BY Orderh.REF Generates error #700 Whereas, the same query executed against a DBISAM DSN works and returns a result set. |
Wed, Sep 19 2018 12:33 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Charles,
<< Is there any solution for users of MS Query, beyond editing the generated SQL, for querying date-type columns in an EDB database? 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:- >> The EDB ODBC Driver was parsing the escapes, but not adding back in the DATE, TIME, or TIMESTAMP prefix, hence the error. I'll have a fix out with the next build 8, which should be available by next week. Tim Young Elevate Software www.elevatesoft.com |
Thu, Sep 20 2018 5:38 AM | Permanent Link |
Charles Bainbridge | Tim Young [Elevate Software] wrote:
<< I'll have a fix out with the next build 8, which should be available by next week. >> That's terrific Tim, thanks. |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |