(sigh) It's not strictly a VFP question, but I'm sure I'll get an answer in the VFP forum.

I have an Outlook form developed on one machine ( NT4.0 SP3-SP5 ) in which I use VbScript to connect to a SQL Server using a DSNless connection. It was originally developed in OL97, migrated to OL98 and finally to OL2K, all development pretty much on the same machine. The form has been successfully opened by several people on different machines that were upgraded from O97 to O2K.

Now the problem - I was recently given a new machine with NT4.0 SP5 and O2K installed. When opening the form, this machine will not successfully establish the DSNless connection to the server. I'm seeing this on other similarly set up machines too.

I trap errors so I know the DAO360 engine and the Workspace (wrkODBC) are being successfully created. Following is the specific code that is failing:

Dim strConnect
strConnect = "ODBC;DRIVER={SQL Server};UID=THE_ID;PWD=THE_PWD;DATABASE=THE_DB;SERVER=THE_SRVR;DSN="
Set GetConnection = Nothing
Set GetConnection = wrkODBC.OpenConnection( "", dbDriverNoPrompt, False, strConnect )

The only things I have changed here are the data specifics for security reasons.

The ODBC Connection Manager in Control Panel verifies that the SQL Server ODBC driver is on the machine ( since I believe it's installed automatically ).

I must have gone brain-dead because I can't figure out what could be different from the older machine to the newer which would cause the DSNless connection to fail on the newer and this thing has worked for months on the older machine.

I would appreciate someone pointing out the specific area of my brain that is dead on this issue.

Thanks,
Bill