ODBC Date Issue

[Jeffrey Ferreira]

Hi All,

We are using ODBC Driver 7.00.
If we do the following in Excel

Select Order_Number, Order_Date from "Open Orders" WHERE  Order Date > "09/01/2022"

it returns every order up until 12/31/2022 and does not return anything from 2023

if  we do

Select Order_Number, Order_Date from "Open Orders" WHERE  Order Date > "01/01/2023"

then it returns the 2023 orders

has anyone ever seen this or know what i could be doing wrong?

thanks
jeff

[Devon Austen]

I can see a few possible issues:

1. your WHERE clause is not using the correct field name. It should be Order_Date not Order Date. You need the underscore and not a space. Then again maybe that is just an issue with typing it out for the forum but it is in both your examples so it could be the issue.

2. Use single quote not double quote.

2. If Order_date is defined with a DATE class you may need to use the date format yyyy-mm-dd in your SQL query.

WHERE Order_Date > '2022-09-01'

[Jeffrey Ferreira]

Devon,

i'm sorry i was just pseudo coding it quick to give you all an idea what i was trying to do

i'm not creating the SQL Select (Excel is).


jeff

[Jeffrey Ferreira]

I just tried it with Excel Power Query and that failed too.  I tested it against another database we have (mysql) and that worked. Is it possible there is something wrong with the 7.00 ODBC Driver. This worked when we were using 4.21.

jeff

[Devon Austen]

I am able to filter based on a date field in Excel just fine.

As I said earlier the issue may be the date format you are trying to use. The ODBC expects YYYY-MM-DD for date fields.

[Jeffrey Ferreira]

Devon can i bug you with one last question...

when you say ODBC  expects YYYY/MM/DD are you saying that my date needs to be stored in the pxplus Data Dictionary as YYYY/MM/DD -> because our dates are stored as MM/DD/YY in the pxplus data dictionary.

or are you just saying the WHERE clause needs to be in 'YYYY/MM/DD' format.

jeff

[Mike King]

Jeff

A couple of things you might try (and why I am suggesting them):

1) If there is no WHERE clause does it return all the orders.  (Checking all records accessible and none have invalid data/keys)

2) Do you have a key on the file based on the date and is it Ascending or Descending? (Perhaps the driver is using an alternate key to access the file and the definition/data is out of sequence)

3) If you add an ORDER BY on the ORDER_NUMBER does the query work? (Try to force the system to use the primary key)

4) What is the CLASS for the Date field in the PxPlus Data Dictionary? (could the class name be incorrect given the data in the record -- if record has dates stored as MMDDYY then the class should be DATE-MMDDYY.

[Jeffrey Ferreira]

Hi Mike

1.) it returns all the data
2.) i did have a key so i tried the order by and it did not work....
     but to be sure i tried on another date field (no key) ...stilll did not work
3.) Order by primary key (no date in key) - did not work
4.) I think the data class might be the problem...

i'm going to take this off line...thanks for the info..

[Devon Austen]

To answer your question I am only referring to the WHERE clause.

and the format is YYYY-MM-DD not YYYY/MM/DD dashes and not forward slashes.

[Jeffrey Ferreira]

So I just spoke to our Product Manager. Our dates in this file use the format:

DATE-MM/DD/AA

the AA was a Legacy Y2K Data Class. Could that be the issue?

jeff

[Devon Austen]

The PxPlus SQL ODBC driver supports that date class.

When using SQL though you use the SQL date format (YYYY-MM-DD) the driver does the conversion to how the date is stored in your file. So assuming your data dictionary has set the date class for the field correctly if you do a SQL query like

SELECT * FROM myTable WHERE datefld > '2022-09-01'

you should get what you want.