Microsoft
Software
Hardware
Network
Question : ODBC works on PC but not Terminal Server
Hi,
I have a MS Access 2007 program that I created on Vista Business connecting to a MS SQL Server 2000 database with 2007 ODBC driver installed on my terminal server. The program runs fine on my PC but not on my terminal server.
When I package the program using the MS Access packaging utilty and install the program on my 64 bit Windows 2003 terminal server I get ODBC errors from some of the fields and object in the program. One of the errors is "Error ODBC - Call failed. 3146" another is "ODBC - connection to CostCode failed". I suspect the problem is with the ODBC set-up but I have checked the ODBC set-up on both machines a few times and both seem to be exactly the same.
Answer : ODBC works on PC but not Terminal Server
There are generally 2 versions of odbc installed on a 64 bit server
to configure 32-bit odbc you should run the following command :
c:\windows\syswow64\odbcad
32.exe
Random Solutions
sum and match result in table
Installing Enterprise Library 3.1 generates "Unable to get installer..." error
MS Office 2003 - Please Insert Disc
web enabled infopath form not able to fetch the data from SQL Server
How Can I Search Exchange 2003 Message Store by subject
Crystal Reports and VB .Net
Exchange Event Log Analysis NDR Backscatter? Intruder?
MS Access change regular number to month in query
datediff -- 2 dates are returning the same datefiff value (i.e. 0)
Access 2003 Insert Query with data from form to multiple records