Sorry. . .I have version 3.07.02. I pulled it off my 4.1 CD. I noticed the driver is not located in the download of the 4.2.x b/a client, unless I missed it. I do have 2 TSM servers, and I was having the problem you describe. I thought I had fixed the issue by creating individual databases for each server and then creating a 3rd database to act as a front end for the 2 individuals. . .that wasn't so good either.
Bud Brown Information Services Systems Administrator 303-436-5986 -----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 10:19 AM To: [EMAIL PROTECTED] Subject: Re: ODBC Driver for Windows This could be APAR IC31451, which is known to occur with the 4.2.0 and 4.2.1 ODBC driver. The problem occurs when you have tables from more than on TSM server linked in the same Access database. I am not aware of any problems such as you describe when the tables are linked to a single TSM server. If that doesn't answer the question, then could you please provide step-by-step details for recreating the problem? As far as being able to indicate whether there is a newer version of the ODBC driver..... I would need to know what version you are currently running in order to answer that! :-) 4.2.1 is the latest available version. 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. "Brown, Bud" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 02/18/2002 09:31 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: ODBC Driver for Windows I was wondering if anybody has had any luck using the ODBC driver and Access 2000 to run read-only queries and run reports on the syscat table. Innitially I have had success in setting this up but that only lasts until I close the database I created. I have to recreate the links every time. I get ODBC connection errors when trying to re-open the database after it has been closed. Could there possibly be a newer version of the driver somewhere? I haven't been able to find it. Bud Brown Information Services Systems Administrator 303-436-5986
