Re: Deploy SQL Express so my app still works on other machines
- From: "Roger Wolter[MSFT]" <rwolter@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 14 May 2006 16:01:47 -0700
Your connection string will cause the application to look for the database
files (mdf and ldf) in the same directory as the application. The files
must be readable and writeable by the Windows user who is running the
application. This all assumes that SQL Express is installed on the user's
machine. If this doesn't help, maybe a more complete description of the
problem than "cannot connect" would help someone figure out what is
happening. If there an error in the SQL Server error logs, what error
message is returned, etc.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"John" <a@xxxxx> wrote in message
news:%23ixhnV5dGHA.3996@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,
I have an app which uses an SQL Express database. The problem I'm
encountering is that when I deploy the app (including installing SQL
Express) my app cannot connect to the database. What is it I have to do to
get this working? Is it the format of my connection string within my app.
I was under the impression developing using SQL Express was
straight-forward (which it was on my dev box) but deploying it and still
having the app working seems a nightmare.
My connection string dev-side is the following:
"Data
Source=.\SQLEXPRESS;AttachDbFileName=|DataDirectory|PM.mdf;Integrated
Security=True;User Instance=True"
Regards
John.
.
- References:
- Prev by Date: Re: MSDE vs SQL Server Express performance
- Next by Date: MSDE and msiexec.exe
- Previous by thread: Deploy SQL Express so my app still works on other machines
- Next by thread: RE: Deploy SQL Express so my app still works on other machines
- Index(es):
Relevant Pages
|