Re: [Emerald] Y2K Bug with Emerald Database and SQL Server when

Dale E. Reed Jr. ( (no email) )
Sun, 21 Feb 1999 20:12:08 -0800

Rudy Komsic wrote:
> I just wanted to report a Y2K bug that I found with SQL 6.5 and the
> subaccounts saexpiredate. What I had to do after the failed Primary key
> changes was to create a whole new Emerald database, transfer all into it,
> then drop the calls table and recreate the calls table with the 5 primary
> keys (added username as primary key). Then I imported only the data from
> the calls table and after that, I deleted my Emerald database and then
> recreated it on a faster drive. Then I transferred it back but after
> transferring it, all the subaccount's saexpiredate got converted to 'Jan 1
> 1900' for some odd reason :(

I'd say this is a transfer problem and has nothing to do with Y2K.

> The way I created the backup database was to generate SQL Script of the
> whole database. could it be possible that Jan 1 1900 was the default of the
> database?
> I finally realized what happened and finally got it fixed.

If you transfer an allow nulls date to a non-null date, then it
will do that.


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.

For more information about this list, including removal,please see