|
Hi Mark, What is the data type on the date field that your inserting your data into? Are you holding the date in a varchar field or in a Date/Time field or in a Date field. How are you viewing the raw data in your table? Could it be that whatever program you're using to view the raw data (presumably you run some SQL statement to see what you've just added), is formatting the date for it's output, but that it's stored correctly? For instance, I have occasion to access some FoxPro tables with ODBC and with a Type 4 JDBC driver and depending on which I use, some values are represented differently. ODBC shows null dates in FoxPro tables as 12/31/1899 while the JDBC driver correctly displays a null or empty string (whichever). Also, I know that I've seen 1 and 0 be represented as 'true' and 'false' by the different drivers as well. It's just how the program chose to represent that data to me. I really wish it wouldn't do that and would just show me the raw data. Back on the Format... I work with DB2 her at work (unfortunately), and dates and times are held in ODBC Date format ({d 'YYYY-MM-DD'} OR {ts 'YYYY-MM-DD HH:MM:SS'}). Should you be formatting similarly? I suppose it depends on the database engine and the data type of the field. Mark Armstrong wrote: OK, |
_______________________________________________ Reply to DFWCFUG: [email protected] Subscribe/Unsubscribe: http://lists1.safesecureweb.com/mailman/listinfo/list List Archives: http://www.mail-archive.com/list%40list.dfwcfug.org/ http://www.mail-archive.com/list%40dfwcfug.org/ DFWCFUG Sponsors: www.HostMySite.com www.teksystems.com/
