Wierd Date field behaviour - the culprit

[rochard]

In Find mode, I type a date into a date time field and get the following error message:

Invalid input '08/12/2002', didn't comply to the format 'MM/DD/YYYY'

On another table, I enter a range 08/12/2002...08/18/2002 and it finds all records.

On another table, a date field will not accept a change.

If this has happened to you, check the format properties. I had set them, inadvertently, to DD-MM-YYYY instead of DD/MM/YYYY and was entering dates as DD/MM/YYYY

[bcusick]

In Find mode, I type a date into a date time field and get the following error message:

Invalid input '08/12/2002', didn't comply to the format 'MM/DD/YYYY'

On another table, I enter a range 08/12/2002...08/18/2002 and it finds all records.

On another table, a date field will not accept a change.

If this has happened to you, check the format properties. I had set them, inadvertently, to DD-MM-YYYY instead of DD/MM/YYYY and was entering dates as DD/MM/YYYY

Michael - when you search for a single day - put a # before it:

'#08/12/2002'

This is because SQL databases use date and TIME. So when you use the # - the SQL Parser writes it as '08/12/2002 00:00:00...08/12/2002 23:59:59'

You only need to do this on SINGLE day searches - or specify the TIME elements as well manually.

Hope this helps,

Bob Cusick

[rochard]

Thanks, Bob. That makes perfect sense.