HP3000-L Archives

September 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Melvin R Rees <[log in to unmask]>
Reply To:
Date:
Wed, 2 Sep 1998 17:52:01 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
I have recently discovered a problem with Allbase, ODBC SE and dates
that some of you may want to watch for.

We converted an Image database to Allbase and then dates ended up
looking like this - 0095-05-30 - in a normal select statement.  This
is fine as our code looks for the missing "19".  However, MS Access
and other ODBC clients display the date as 05/30/00 or 05/30/1900.
Identical data in MS SQL or Interbase display fine.  This leads me to
suspect the ODBC drivers. The dates work fine if they have 4 digit
years.

The interesting thing is not that the dates are wrong but that Access
treats the year 0095 as 1900.  Actually all 2 digit years are
displayed as 1900 like 05/30/1900.  But data with 4 digit years are
displayed with 2 digit years like 05/30/92 (wierd).

Anyway, for you people who are using Allbase ake sure your dates have
4 digit years.

Rgds
Mel Rees
[log in to unmask]

ATOM RSS1 RSS2