Re: ODBC Weirdness...

[Pete Hall <pbhall@xxxxxxxxxx>]

At 17:08 01/22/2002, Tim Hatzenbeler wrote:
>I think I set something up wrong, but I don't know what to change...
>....
>I have created a system DSN  via the ODBC connections called    Trackerodbc
>and I have set up my default library with this connection to be  TIMTEST
>
>When I try to design a report with crystal reports the first time I
>reference the tables of that odbc connection I get the correct library and
>the correct tables (files)... But If I try to add another table, It no
>longer retrieves same files in timedata, instead I'm presented with the
>tables in the default system libraries .. IE: QGPL...
>
>So to correct this problem I have to close down the reports, and signoff the
>odbc connection

It's been a couple of years (and releases of Crystal Reports), but last
time I looked, Crystal was storing the connection information internally in
the report, and only using the ODBC definition to initially connect to the
host. I'm suspicious that this is a Crystal problem, possibly aggravated by
some IBM unique driver "feature". In my experience, Seagate is unwilling to
communicate with IBM on any level, so don't expect to get much in the way
of help from them. IBM will charge you to help, but at least they have some
knowledge of what the specification is supposed to do, and may possibly
even be able to suggest an obscure switch setting that will help. An ODBC
trace might give you a hint.

I got genuinely tired of dealing with Crystal-IBM problems. I recommend
against using Crystal for anything mission critical. It's a good product,
but (as of 2 years ago) support sucks. Good luck and happy finger pointing.

Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall/