Connection String in SQL Server 2005 giving errors

HELP


I moved a database and application created in MS SQL Server 2000 to
MS SQL 2005 Express. And when I run the applications I am getting 'SQL
Server does not exists or Access Denied' error.

I can find nothing wrong with the connection string that I am using,
so I tried an old trick to create a new one on the MS SQL 2005 Express
machine

Create a blank file in notepas and name it something.udl
Double click on something.udl
It will open the UDL creator asking for Server etc.
I could not get this to find the SQL Server either using (local) or
Drop down or SQLExpress

HELP

How can I find out what is wrong with my connection string?

Mark Moss


.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Connecting to DB with Static IP over the internet
    ... I was getting mental over this because the settings on the sql server i did ... item on the connection string. ... stuff from the internet. ...
    (microsoft.public.sqlserver.setup)
  • Re: Access Retirement
    ... Access can link to SQL Server tables or views via ODBC. ... to existing applications if they're going to be replaced soon anyway. ... >>> Access 97 support. ...
    (microsoft.public.access.conversion)
  • Integrated security with IIS 6.0 without explicit Anonymous a/c ri
    ... previleges in SQL Server Database to be used through connection string by IIS ... So what I am thinking of is using Windows Only ...
    (microsoft.public.sqlserver.server)
  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... Look up sp_attachdb in the books online with SQL Server Express. ... You will no longer need the database MDF file name in the connection string. ... the simplest way is to not use USER INSTANCE. ...
    (microsoft.public.dotnet.framework.aspnet)