Whoooops, I think I suffered a serious "brain-check"... I Didn't mean to
sound like I wasn't concerned with this issue! I meant to say I wasn't
concerned with the rest of the stuff that the diagnostics section asks
for. Sorry about that!
This should have read:
Please follow the instructions in the "Troubleshooting/Diagnostics"
section of the README.ODBC.TXT file to obtain traces of the problem, then
open a problem with IBM support and provide them with the trace
documentation. (I'm not so concerned with the other items that the README
asks for.) Crystal Reports is not formally supported (i.e. we don't test
it), so support is on a "best effort" basis. However, we are interested in
understanding problems like this with the ODBC driver and fixing them when
possible, so you shouldn't be flat-out refused (it even says so in the
README file!).
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Andrew Raibeck/Tucson/IBM@IBMUS
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/20/2001 11:46
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: ODBC and TSM timestamp data type (Crystal Reports)
Bill and Ken,
Please follow the instructions in the "Troubleshooting/Diagnostics"
section of the README.ODBC.TXT file to obtain traces of the problem, then
open a problem with IBM support and provide them with the trace
documentation (I'm not so concerned. Crystal Reports is not formally
supported (i.e. we don't test it), so support is on a "best effort" basis.
However, we are interested in understanding problems like this with the
ODBC driver and fixing them when possible, so you shouldn't be flat-out
refused (it even says so in the README file!).
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
William Boyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/20/2001 11:16
Please respond to bill.boyer
To: [EMAIL PROTECTED]
cc:
Subject: Re: ODBC and TSM timestamp data type (Crystal
Reports)
I have the same problems. If I use Access or Excel to get the data via the
same ODBC connection, the date/times are correct. Also, if you use a
utility
that Seagate distributes on the CD called SQLCON32.EXE with the same
select
statement I cut and pasted from my report, it displays correctly. I went
through this with the email tech support and finally had to call in and
open
a problem. They sent me the latest patches for CR8.5, but they didn't have
any effect. I just haven't had the time to call back in and break the new
to
them.
If you come up with a solution, PLEASE post it!!!!?????!?!
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Ken Long
Sent: Tuesday, November 20, 2001 12:04 PM
To: [EMAIL PROTECTED]
Subject: ODBC and TSM timestamp data type (Crystal Reports)
I know some of you are running Crystal Reports against the TSM database,
hopefully you can steer me straight.
I can't get Crystal to render any of the TSM timestamp fields - I always
get 0's for the timestamp. For example, the Start_Time field on the
Summary table. All times display as 12:00:00 am. Browsing the data for
the data for the field shows: DateTime(0,0,0,00,00,00).
Needless to say, this makes it difficult to just show results from
yesterday.
I'm using Seagate Crystal Reports 8.0.1.1 and the TSM ODBC driver
4.02.01.00 (part of the 4.2.1 Win32 client.) ODBCADSM.DLL is dated
8/3/2001.
Any help would be appreciated.
Thanks... Ken
