I would like to know what steps I need to take to ensure my app. works on
January 1st.  I am using Delphi 4 with Paradox 7 tables.  I realize I need
to go to the BDE settings and change my date/time settings to four digits.
What is required for the Paradox 7 table settings themselves?  Is there a
Y2K change that forces the tables to actually store the data as four digits
and therefore allows submission of queries etc?  thanks

I would like to know that, too!

Arne.

<7tigv9$p...@forums.borland.com>...

I would like to know that, too!

Arne.

<7tigv9$p...@forums.borland.com>...

All date info is Y2K compliant. Read Inprise's White Paper. Just be
sure you give the proper interpretation to the user's data.

<7tigv9$p...@forums.borland.com>...

Put shortDateFormat := 'mm/dd/yyyy' (or something similar)
in the oncreate of your mainform too

news:7tigv9$piq1@forums.borland.com...

Paradox tables have stored the full date since version 1.0 for DOS. You may
want to add the line

ShortDateFormat := 'mm/dd/yyyy';

to your main form's OnCreate event handler to ensure that dates are
displayed with four digit years in your app regardless of the Windows
Control Panel settings.

Bill

--

Bill Todd - TeamB
(TeamB cannot respond to questions received via email)

Thanks (important information that all versions of
paradox have yyyy format).

Arne.

But how are the Date values stored in Paradox tables actually? Is it
some running float number of seconds, starting from 1970 or something,
a la Unix.

I mean, when you test Paradox database with Norton 2000 test application,
it always reports the databases non y2k compliant, and severity level
being 3.
I don't remember the exact report message, but it was something like
"Proprietary Date format".

The whole Norton 2000 test package looks and feels very clumsy, I don't
like that user interface at all. But it seems to have some popularity
anyway.
Fortunately we are not alone, also MS-Office 97 package affects some
y2k-notifications from Norton 2000.

Markku Nevalainen

I believe if you check Borland's Y2K site, your questions will
be answered.  The 0 date varied in different versions of the
BDE and required a little programming when I moved from D1
(16 bit) to D3 (32 bit).  If you choose to use 2 digit years, you are likely
to run
into problems as indicated on Borland's site because even
the 32 bit versions of the BDE were somewhat inconsistent.
If you are 32 bit and using 4 digit years you and your customers
should have little to worry about.  But be sure to read the Borland
site because there are a couple of issues in the older 32 bit versions.
If you are still doing 16 bit, hope you aren't using dates!

In Paradox tables dates are stored as a number with 1 begin 01/01/0001

--
Brian Bushay (TeamB)
Bbus...@NMPLS.com

Please, give me some exact Borland reference to THAT information!!

I better do believe what Team-B said, that the Paradox Date field is a floating
number of days, that is counted starting from 01/01/0001.

What 2 digits exactly are you talking about here? Those settings from Windows
Control Panel, or settings from BDE Config?

I think that neither of these settings has any effect. Paradox will always
save the date stamp as a running float, that started 01/01/0001, and there's
no way you can affect to this inside your program, no matter what your
Windows or BDE settings are. Of course there are still the hacker ways,
to do what you want with those field values.

This statement also looks quite odd. I can create Paradox 5.0 tables on
D3/BDE 4.51, and then happily use them with D1/BDE 2.52. Or vice versa,
create with D1 and then use with D3.

This is due to that fact, that the Paradox 4.0 and 5.0 database formats
are exactly the same for both 16-bit and 32-bit Delphi versions. And also,
in both cases the Date field content is always just running float number,
that was started 01/01/0001.
And that's why you should have no worries when the clock turns to Jan 1 2000.
For the Date field, it is just like any other day, just one number more to
that running value.

For what I think, the problem I mentioned with Norton 2000 test program
is, that it does not know how the contents of Paradox Date field should
be understood. That's why it reports several DB-files not being non-y2k
compliant, and seeing that scares the s..t out of customers.  There seems
not be any newer version from Peter Norton, where test would report Paradox
fields to be y2k-proof.

Of course I can be wrong here. And that's why, any comments on this matter??

Markku Nevalainen

The base date for Paradox dates has been 1/1/0001 since version 1.0 for DOS.
It has never changed.

Bill

--

Bill Todd - TeamB
(TeamB cannot respond to questions received via email)

Thinking back, I guess my problems were
with null dates.  In D1 they displayed as blanks.
In D3 they displayed as a date in 1899.  I presumed
that the BDE was internally treating them as a zero date.
Sorry for the incorrect statement.  I'm getting old
and my memory is imperfect sometimes.

Here is Borland's Y2K info:
http://www.borland.com/about/y2000/productlist.html

In any case, D1 is not being tested by Borland if
I understand their site correctly.  And
the prudent thing to do is to use 4 digit years.
The easiest way to ensure that is to
start your programs with
shortdateformat := 'mm/dd/yyyy' or something similar.