Provider not specified and there is no designated default provider

noreply@blogger.com (.) — Thu, 13 Apr 2006 13:29:00 +0000

I was getting the following error on our new Dell 6850 server with Win2003 64bit and SQL Server 2005 64bit:

"Provider not specified and there is no designated default provider"

Having looked at this page:

http://www.codingforums.com/archive/index.php?t-66468.html (Last post)

It seemed the problem was due to Windows not having a 64 bit version of a database driver. After looking at the advice on the linking page I was still not able to get it going, so I did some experimenting and found the answer.

My old code looked like:

Set conn = Server.CreateObject("ADODB.Connection")
conn.ConnectionString = "DSN=MyDSN;UID=MyUser;PWD=MyPassword"
conn.Mode = adModeReadWrite
conn.Open
Set rs = Server.CreateObject("ADODB.Recordset")

Which I changed to:

Set conn = Server.CreateObject("ADODB.Connection")
conn.ConnectionString = "Provider=SQLOLEDB;UserID=MyUser;Password=MyPassword;
Database=MyDatabase"
conn.Mode = adModeReadWrite
conn.Open
Set rs = Server.CreateObject("ADODB.Recordset")

The fix works slightly different and does not rely on a DSN, which for me was no bad thing.

Global.asa file doesn't work

noreply@blogger.com (.) — Thu, 06 Apr 2006 13:57:00 +0000

I was editing global.asa today and seeing no affect on my web app.

The problem was that my app was a sub-directory, and hence was not a proper web app, and therefore didn't execute the global.asa file.

The fix for this is to turn your sub-directory into an application. This is done by right-clicking and selecting Properties, and then clicking the 'Create' button to make it into an app.

ASP Programming

Provider not specified and there is no designated default provider

Global.asa file doesn't work