How will i know that my 32 bit application is tryting to connect to sql server using sql 2005 or sql 2008 drivers (sql native client)

Question

0.00/5 (No votes)

See more:

Hi,

How will i come to know - that wether my 32 bit application(c++) is using SQL native client 2005 drivers or SQL native client 2008 drivers to connect to SQL server?

In the connection string it has been mentioned that <b>Provider=SQLNCLI10.1;</b> , by which i understand sql nativeclient 2008 is used.

I have problem that, my application crashes when sql native client 2005 is not installed. Because it tries to load sqlncli.dll and crashes if its not there.
Works well with SQL client 2005. My application need to upgrade to SQL serve 2008, hence the problem.

How will i know - that wether my 32 bit application(c++) is using SQL native client 2005 drivers or SQL native client 2008 drivers to connect to SQL server?

Any thoghts on this would be of great help.

Posted 10-Dec-11 0:15am

kapparmath

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

jschell · Answer 1 · 2012-01-28T06:13:00

You might able to catch the system exception which is causing the crash.

However it might just be better if you wrote code that actually looked for the required dll(s). You can either just do a file search, or probably better try to load the dll yourself (unload it also if you find it.) You need only do that when the application starts.