Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1092213
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T23:38:52+00:00 2026-05-16T23:38:52+00:00

I am using SQL Server Workgroup Edition on Windows Server 2003 R2 My classic

  • 0

I am using SQL Server Workgroup Edition on Windows Server 2003 R2

My classic ASP pages access my production database using a system DSN. All working here.

Code like this…

<%
dbName= "ProdDB"  
userID = "PublicUser"  
pwd = "PublicUserPW"

Set objConn = Server.createObject("ADODB.Connection")  
objConn.connectionString = "DSN=MySystemDSN"  
objConn.open dbName, userID, pwd  
%>  

For development and testing, I created a copy of ProdDB in Enterprise Manager by

  • Backing up ProdDB
  • Restoring from the ProdDB backup set to a new database called TestDB

My understanding was that the restored database would contain an exact copy of the data as well as users, roles etc. Comparing both databases in Enterprise Manager seemed to back up this assumption.

So… I assumed I can access the test copy using the same credentials and only change the dbName, like so…

<%
dbName= "TestDB"  
userID = "PublicUser"  
pwd = "PublicUserPW"

Set objConn = Server.createObject("ADODB.Connection")  
objConn.connectionString = "DSN=MySystemDSN"  
objConn.open dbName, userID, pwd  
%>  

However, now my page returns

[Microsoft][ODBC Driver Manager] Data
source name not found and no default
driver specified

I have even tried creating a new System DSN, with a default database pointing at TestDB. Still no joy.

I’m sure I’m doing something simple and silly. Any assistance gratefully received.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T23:38:53+00:00Added an answer on May 16, 2026 at 11:38 pm

    The documentation for the open method says it’s declared:

    connection.Open ConnectionString, UserID, Password, Options
    

    So it looks like you’re passing in TestDB as the connection string. I usually call open without specifying any arguments. Grab a connection string from connectionstrings dot com, and:

    objConn.ConnectionString = "Data Source=localhost;Initial Catalog=testdb;" & _
        "User Id=myUsername;Password=myPassword;"
    objConn.Open
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Using SQL Server 2005 developer edition on Windows XP pro (32-bit) I notice that
I installed and configured SQL Server 2005 with Reporting Services, Workgroup Edition on Windows
using SQL Server 2005 with SP4 and I am designing a database table. Here
Using SQL Server 2005 I have the server connection name as (server1) in windows
Using SQL Server, what is a simple but effective means of denying access to
Using SQL Server Management Studio, I have backed up a database from one server
I am using SQL Server Express 2005. I have a single database myDB I
I am using SQL Server Express 2005. I have only a single database to
I am using IIS 6.0 on Windows 2003 in a workgroup, and have created
Using SQL Server, how do I split a string so I can access item

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.