Kevin; I haven't connect UD to SQL server since version 6.0.12 so - hopefully - my comments are dated. We had a VB app that connected using UniOLEDB. I had some trouble with different versions - 1 would work with Access but not Excel and another was the opposite. Setting up the connection strings/uci.config etc was strange. Even under windows some things were case sensitive which normally weren't under windows (I don't recall offhand precisely what it was - the path or the name of the UCI... something that as soon as I matched the case worked).
The only other issue we had was the inclusion of certain characters in the users passwords that were used to connect to the UD server - ';' and '&' were the biggest offenders. Not sure if it was the connection or the VB code making the connection where it caused the problem. I only set up the linked server as a proof of concept that never went anywhere so I haven't had to look at it since. Hth Colin Alfke Calgary, Canada -----Original Message----- From: Kevin King I'm wondering if the problem might be the provider string in setting up the SQL Server linked server. Looking at the IBM/Rocket documentation I'm not seeing a single word about what this provider string is supposed to look like. The client currently has this provider string for the UniOLEDB driver: ODBC;DataSource=ADS;DSN=ADS;SRV=ADS;DBQ=/ud/XXX;DATABASE= ...and as far as I have heard it works on one SQL Server instance, but fails miserably on an exact duplicate system. Two systems, identical in every way with the exception of distinct SQL Server database instances, same U2 ODBC and OLEDB drivers, and yet one works and the other... blows chunks with "catastrophic failure" and stuff like that. Ideas? -Kevin _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
