The column is a DATE. I tried changing this to a DATETIME but the same error occurred. Interestingly - I have other tables with a DATETIME that work fine.
The only difference to take into account though is that all the datetime columns are system generated where as the date field that is throwing read errors has orginated from a form field. This field is correctly inserted into the database but then has the parse error on the read. If I had errors on my local machine I would point the finger at the code but as it works fine and only fails on my service provider's server I am thinking it has to be something else? Andrew Quoting Graeme J Sweeney <[EMAIL PROTECTED]>: > On Tue, 20 Mar 2007, [EMAIL PROTECTED] wrote: > > > Thanks for the response. I'll have a look at the example you have > > suggested. I am using a date jdbc type for the date field as I only > > need dates in the form yyyy-MM-dd rather than the extended datetime > > format. > > Is the column type DATE or DATETIME ? > > -- > Graeme - >
