Oct 30 16:35:46.61: [1] START <br>Oct 30 16:35:46.61: [15] DB Connect <br>Oct 30 16:35:46.61: ConnectString: DSN=Dispatch <br>Oct 30 16:35:46.74: ERROR: Connect: SQLConnect failed. <br>Oct 30 16:35:46.74: SQL Error State: S1000 <br> Native Error Code: AB <br> ODBC Error: [Microsoft][ODBC Visual FoxPro Driver]Cannot open file v:\dispatch_central\dbf\sys2000.dbc. <br>Oct 30 16:35:46.74: SQL Error State: 01000 <br> Native Error Code: 0 <br> ODBC Error: [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). <br>Oct 30 16:35:46.74: FAILURE <br>Oct 30 16:35:46.74: ERROR: Missing next step <br>Oct 30 16:35:46.74: FATAL <br>Oct 30 16:35:46.74: Attempting to jump to Fatal Error Global Event label: '' <br>Oct 30 16:35:46.74: Fatal label undefined! <br>Oct 30 16:35:46.74: Attempting ag_unlisten, lines[curLine].chdev = 0x1 <br>Oct 30 16:35:46.74: ag_unlisten - success <br>Oct 30 16:35:46.74: dx_close <br>Oct 30 16:35:46.75: ReleaseLine done. <br>Oct 30 16:35:46.77: All memory released. Exiting...

Sorry a little quick on the enter key. I am having trouble with the DB Connect statement. I am able to get this to work in simulation mode, but not with the production server. I am using Dialogic 5.1 with sp1. Its a windows 2000 server. I have tested the ODBC dsn. It works in other programs that reference it. The step works fine on my developement machine (windows XP Pro).

The only answer that we can see for this is that you are using a different obbc driver on your computer running simulator and the production server. Please let us know what each of them are for future reference.

Ok, I've narrowed it down a bit. On 3 different machines I can run the db lookup via the simulator just fine. My developement machine can also run via the simulator fine. When I try it via the dialogic card it fails on the db connect step.

Could you try setting your *application*.TAL file to only run one port and let us know what happens. <br>If that works, then I believe your database is not set to accept multiple connects via the odbc. I know that one usually doesn't have these kinds of problems from foxpro though...

I actually have it set to one port. I have a 16 port analog card, but I am only using 1 port. Its port #3, if that makes a difference.

Are you running TFServer as a service? If so, stop the service (using Windows Service Control Manager, and exit the SCM before next step), and run TFServer in a console window. Simply open a Command Prompt and type, "tfserver". It should come back with "TFServer running in console mode". Let it run and check your logs. It is possible that TFServer may not have sufficient rights to read/write to that database.

You got it. It was the rights on the TFServer service . I modified the logon rights to the tfserver service and everything works fine now. I really appreciate your persistence