On Mon, 21 Jun 1999 01:13:37 +0100, gerard <gerard_at_xsoft.demon.co.uk>
wrote:
>Has anyone experienced this problem.
>
>We have MS Access97 connected to Oracle 8 using ODBC.
>A column in Oracle is of type DATE.
>An access field is bound to this column. If you enter a date into
>this field all is ok. You can go back to the field and change the date
>with no problem. But if you delete the date, move out of the field and
>then back into the field again, a garbage date appears, usually
>01/11/20. You then can't delete this date at all. You get a dialogue
>box that tells you that someone else has changed the data.
>The only way to remove this garbage date is through SQLPLUS.
>On a date oriented app this bug is most infuriating, and I can't see
>any way of tracking down where the fault lies.
>
>Help please
>
>regards gerard
The best way to see what is going on would be to enable an ODBC trace
and see what Access is doing to Oracle. Either Access is defaulting
the date, or the ODBC is, or the RDBMS is (you can check the column
defaults at the RDBMS level). I doubt the database is the one with
this default set...
Received on Mon Jun 21 1999 - 10:45:55 CDT
