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
Problem using WITH XMLNAMESPACES with nested queries
Visual Studio 2008 C# XNA - Creating a timer sequence for updated objects
Adding the record count of one table into another
[Microsoft][ODBC Microsoft Access Driver] Too many client tasks.
TextBox and Validation Rule
.NET MySQL question
Difficulty uploading items larger than 1 MB
TC5730 Thin Client WES 2009 Terminal Services 2008 Single Sign On issue (0x507?)
Can a Dell XP Home reinstallation cd for a PC be used for reinstallation of XP Home on Dell laptop without having any issues?
MFC7 CDHtmlDialog: How to cancel a navigation in OnBeforeNavigate