Jonas Eriksson

Now I've left ODBC for WPE, XML & XSLT. But it would still be of interest to startup the ODBC for some use in the future.

Hi! Perhaps we have the exact same problem. I've tried connecting to FM on the same computer (localhost) to FMPro, and to FMSA. Why do you believe that Sequelink think you're accessing a server? If you're using localhost (or 127.0.0.1) it speaks to the port 2399 on the local computer. If you write [netstat -a] in your commandprompt do you se something listening on port 2399? You should, but I dont.

Thank you for your thoughts, but the files and the odbcclient are on the same computer (at least until its been tested ok). I am still searching for answers, but I am a little stuck, so meantime I am rewriting my code to use the WPE instead of ODBC.

Hi! I lost my ODBC-connection. Very confusing. The ODBC-client driver SequeLink says error 2306 "TCP/IP Error, connection refused" (on localhost, port 2399). Found a suggestion in the DataDirect-helpfiles to run netstat -a to see if the server is listening on port 2399, its not. Is it the xDBC plugin that has stopped to work? ODBC is allowed in FMSA admin. Everything else works fine, including WPE. ODBC has been running fine on our Win2000Server for months until last friday when we had to take the PDC (Win2003SBS) offline a short while to make more space on the system partition (for that reason we moved the mailserver-files to another partition). Cannot see why that should affect our FMSA odbc-functions, can you? Greatful for any suggestions!