Taking a stab in the dark connecting an application to system DSN to SQL Server 2005
Posted on 2011-05-09
I have an application developed by a former colleague who has left the company without leaving any documentation or source code.
The application is simple enough, it is to allow user to query a database in order for them to do audits / statistical analysis.
The application connects to the System DSN which is connected to the SQL Server.
We have not been having any problems until we had to do a migration.
Previously the application connects to DSN to SQL Server 2000.
Now, the SQL Server has been moved to another server and upgraded to SQL Server 2005.
DSN has been reconfigured, and there are no errors when setting up DSN. Connectivity test is good too.
When I tried running the application, it gives me "ODBC --Call Failed" error message.
I copied the application and a copy of the database locally, uploaded the database to SQL Server 2005 and configured the DSN and the application works fine.
The application is in *.mde format.
So far, the pattern that I noticed is that the server where I'm moving my database to does not have Microsoft Access installed, but I don't think this would be a problem, would it?
any pointers to the right direction will be appreciated!