OK, thanks for the info. If you are running the 3.7.2 ODBC driver, then
that is definitely an issue.

The Office 2000 products were not even supported until 4.2. Even on an
"unofficial" basis, I didn't have any luck myself getting Access 2000 to
work with an ODBC driver below 4.2. If you were able to get it to work at
all, you were doing better than I.

Starting with 4.2, the ODBC driver is a separate package from the B-A
client. If you pulled the 4.2 client from the FTP site, then you should
find the ODBC driver out there as well (it'll have ODBC_DRIVER as part of
the file name, and is around 13 MB).

The 4.2 ODBC driver should work fine as long as you stick to accessing one
TSM server per Access database. The problem with tables from multiple TSM
servers should be fixed in 4.2.2 and up, probably around the April-May
timeframe.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

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" <Bud.Brown AT DHHA DOT ORG>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/18/2002 11:06
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: ODBC Driver for Windows



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