Dear Fellow Zope Users, Many thanks go to the following persons for their patient assistance. Henny van der Linde, Julio Dinis and Julio Silva Success at last. Here, finally is what I had to do. After installing the ZODBC DA, I needed to ensure that the Zope server runs as a known username (with a known password). Then I needed to create a Windows NT account to correspond to that username and password. Next I needed to ensure that the SQL Server admits a login using that combination of username and password with at least dbowner access to the database I want the ZOPE server to use. Once I did that, I was able to simply choose a DSN from the list box that appears on the add ODBC connection screen and it worked. It all came together when Julio Dinis asked me if the server I was trying to connect to was a remote server or a local (on the same machine as the ZOPE installation) SQL server. When I tried it on a local SQL Server DSN it worked, but when I tried it on my remote SQL Server it worked. When Henny van der Linde suggested I use SQL Server's logging to see if the connections were being rejected, I saw that ZOPE was trying to establish a trusted connection with an undefined username. That was when I finally figured out what I needed to do. And I was just about to give up on ZOPE. Good thing I did not. Perhaps they need to update the documentation. If you need any further explanation of the setup, drop me a line. Original Question:

Anyone ever figured out how to get ZOPE's ODBC DA to work with MS SQL Server?

I am a Zope newbie using MS SQL Server 7.0, Zope version 2.1.6, Python 1.5.2 Win 386 and ZODBC Version 3.1.0b2.

Whenever I attempt to open an ODBC connection to the SQL Server I get the message "Invalid connection string:" followed by the name of the DSN I am trying to use. Can anyone help me along with this or is this the curse for using Microsoft software?

Yours sincerely, Robert Honore.