Re: Problem with DateTimes and SQL Server 2000

[Arjan Hoornstra <ahoor@YAHOO.COM>]

Well, some serious downgrading here...
anyway, if you really want that, you may want to look at the format
your outputdate is in. The default Sybase date format is 'Mon d yyyy
hh:mm' ie. May 3 2001 4:57PM. For SQL-server this may be different. At
least, I suppose the sp worked fine in Sybase.
So you may want to convert the outputted date to a readable value in
the sp, or keep using the char(20).... what is the problem with that?

Arjan


--- Chris Gin <Chris_Gin@CARDLINK.CO.NZ> wrote:
> Hi,
>
> We are in the process of migrating our SQR programs from Unix/Sybase
> to
> NT/SQL Server 2000. We have come across one serious problem which
> causes SQR
> to GPF.
>
> It seems that if we execute a stored procedure containing a datetime
> field
> in the result set, SQR crashes.
>
> Interestingly, it only happens if the &variable is declared as a
> datetime in
> SQR - if we declare it as a char(), then it seems to work even if the
> procedure still returns a datetime.
>
> ie. This fails
>
> execute do=print_data get_accounts into &account_no int, &start_date
> datetime
>
> but this works
>
> execute do=print_data get_accounts into &account_no int, &start_date
> char(20)
>
>
> We are using SQR 6.1.3 with SQL Server 2000 running on Windows 2000.
> The
> unix version we were using was version 4.3.2.2.
>
> Does anyone have any ideas on what's causing this?
>
> Thanks,
> Chris


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/