Main Board > ODBC

ODBC Date Issue

<< < (2/3) > >>

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page