I am madly trying to finish a WP procedure from LH to SQl Server (6.5), but the DATE column is giving me grief. I have defined it as 'datetime' in SQL server and 'DATETIME(19)' in my dataset. Whatever date format I try keeps giving me garbage (12/31/67 0:00AM). I have tried mdy, dmy, ymd etc etc, sometimes the month comes right, but never the year. What else can I look at? I use both the Query tool in OI and the ISQL/w tool in SQL server to look at my results.

Hi Nick,

I am madly trying to finish a WP procedure from LH to SQl Server (6.5), but the DATE column is giving me grief. I have defined it as 'datetime' in SQL server and 'DATETIME(19)' in my dataset. Whatever date format I try keeps giving me garbage (12/31/67 0:00AM). I have tried mdy, dmy, ymd etc etc, sometimes the month comes right, but never the year. What else can I look at? I use both the Query tool in OI and the ISQL/w tool in SQL server to look at my results.

12/31/67 0:00AM is the "zero date" for OpenInsight. It means that you are warehousing one of the following values:

1. A zero-length string

2. An integer value of zero

3. A string value which cannot be converted to a number by OpenInsight

I am guessing that you are seeing #3. The value being set to the DataSet should be in OpenInsight internal date format. (For example, today is 11180.) Make sure you are not converting the value to a string format, such as "08/10/98".

Cameron Purdy

Revelation Software

You know, Cameron, you are absolutely right. I just "assumed" you had to populate the datasets in OCONV formats. The erroneous date did look kind of familiar, but it never dawned…. Thanks (again)

Hi Nick,

It isn't the first time that a second pair of eyes have solved a problem! Glad to be able to help,

Cameron Purdy

Revelation Software

View this thread on the forum...