ODBCDBE and DSN

[rdonnay]

I am helping a customer with my first VFP conversion project.
Developing the screens turned out to be the easiest part of the project - thanks to eXpress++.

Now I am trying to connect to their SQL Server using the same connection string as the FoxPro application.
The connection fails.

I have connected to SQL Server in other applications with no problem.
This is the first time I have tried to connect via a DSN.
Is anybody out there using ODBCDBE and a DSN?

Examples of my connect string:

DBE=ODBCDBE; DSN=RMS_DSN; UID=RMS5; PWD=; CONNECTTIMEOUT=15;

[Tom]

What about the database name (DBQ)?

[rdonnay]

The problem is that the server connection is one of the parameters that is passed to the program.
I'm going to have difficulty getting them to change it. It's passed from a VFP program to the Xbase++ program.

I'm going to see if there is a way I can query the DSN and parse it out.

Alaska documentation shows how to use a DSN and I am using it correctly.
The error returned is 5381. I can't find anything about this error except I have seen it before with the ADSDBE.
It happened when using the old ACE client DLLs with the most current ADSDBE.DLL.

I sent a support request to Alaska on this issue. Due to the fact that it is the first VFP conversion project I am hoping they give this some priority.