Bill, Do you have any idea where the 07/31/2008 date is coming from? Obviously, it's not a valid date in a DDMMYYYY format, but some eep or computed column or stored procedure or rule or SET VAR somewhere is trying to create that as a date.
Are you so close to Canada that you have to use those goofy Canadian dates? Bill On Mon, Sep 29, 2008 at 2:15 PM, Bill Niehaus <[EMAIL PROTECTED]>wrote: > When I try to edit a date in a table by using a command like "Edit all in > table where harvestDate = '01/01/01' I get a screen with records showing. > When I try to edit the field harvestDate for one of the records, I get an > error "07/31/2008" is not a valid date. I get the same problem when trying > to edit a date in a form also (I'm not using a date picket). > > If I use the following command, it works fine with the database. > > update trialno set harvestdate = '08/04/2008' where trial = '088741' > > My input setting for date is set at DDMMYYYY. > > I just updated to 7.6.4.30919 > > Thanks. > > Bill Niehaus > > >
