Connecting to SQL dbfs with existing code

We recently moved our Access databases to SQL and are
trying to get our pages to open the connections to the
server. I've set the system DSNs on the server as needed.
However, no connections are made. After reviewing several
books, microsoft.com, etc...I'm severely frustrated. The
only thing I can think that would possibly be an issue is
that our webserver (Win2003) is not setup as a Primary
Domain Server and we have to connect via http.
Any suggestions are appreciated. THANKS!Does the System DSN connect if you Test it from the IIS server?
If not what is the OS error returned?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connecting to external data source

I have found several pages demonstrating this but I still cannot make it
work. I need to connect to an external data source. I have a user DSN named
"OMD" which does not require a username or password. My connection will be
read-only. My intent is to use SQLConnect, although I am open to any
suggestions. I have tried various methods of connecting to Access databases,
figuring that would be easier and then I could connect to my OMD source, but
I have not been able to connect to any other data source. Any words of
encouragement would be appreciated.
How exactly are you trying to connect to external data sources? Linked
servers? Openrowset? Opendatasource? Openquery?
What steps did you take to set this up with SQL Server?
What errors are you getting? What specific types of data sources are
you trying to connect to - e.g. Access, FoxPro, Oracle, Sybase, etc?
I'm not real clear on what it is you are trying to connect to from
where and what the errors are.
-Sue
On Tue, 19 Oct 2004 09:29:12 -0700, Phil T
<PhilT@.discussions.microsoft.com> wrote:

>I have found several pages demonstrating this but I still cannot make it
>work. I need to connect to an external data source. I have a user DSN named
>"OMD" which does not require a username or password. My connection will be
>read-only. My intent is to use SQLConnect, although I am open to any
>suggestions. I have tried various methods of connecting to Access databases,
>figuring that would be easier and then I could connect to my OMD source, but
>I have not been able to connect to any other data source. Any words of
>encouragement would be appreciated.
|||I am trying to connect the the source any way I can.
I have tried Openrowset, openquery, sp_addlinkedserver, sqlconnect,
sqldriverconnect.
I have an ODBC connection named OMD that connects using the Transoft OMD
driver. (Although I have not successfully connected to any type of dtabase;
not even other SQL servers)
It seems to me that sqlconnect is the easiest way to connect. Since there
is no username or password required by the ODBC driver, I thought simply using
declare @.mycode int
@.mycode=sqlconnect(dsn='OMD')
should work. It does not. I would like the proper syntax required.
Somehow I am misinterpreting the examples in the Help files. Please excuse
my ignorance.
Since the code will not compile, I am not getting to the point of errors.
Thanks for replying.
Phil
"Sue Hoegemeier" wrote:

> How exactly are you trying to connect to external data sources? Linked
> servers? Openrowset? Opendatasource? Openquery?
> What steps did you take to set this up with SQL Server?
> What errors are you getting? What specific types of data sources are
> you trying to connect to - e.g. Access, FoxPro, Oracle, Sybase, etc?
> I'm not real clear on what it is you are trying to connect to from
> where and what the errors are.
> -Sue
> On Tue, 19 Oct 2004 09:29:12 -0700, Phil T
> <PhilT@.discussions.microsoft.com> wrote:
>
>
|||If your code won't compile then your first issue is more of
an issue with whatever language you are using and how to
code data access routines. There is no one generic response
on how to do this with any data source and in any language.
In any case, are you trying to code this using the ODBC
APIs? If so, you need to use SQLConnect("DSN-Name") .
It would probably be easier to help you out if you could
post what language you are trying to do this in, what syntax
errors you receive, what the code is that is failing and
what examples you are trying to follow.
-Sue
On Mon, 1 Nov 2004 09:44:05 -0800, Phil T
<PhilT@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am trying to connect the the source any way I can.
>I have tried Openrowset, openquery, sp_addlinkedserver, sqlconnect,
>sqldriverconnect.
>I have an ODBC connection named OMD that connects using the Transoft OMD
>driver. (Although I have not successfully connected to any type of dtabase;
>not even other SQL servers)
>It seems to me that sqlconnect is the easiest way to connect. Since there
>is no username or password required by the ODBC driver, I thought simply using
>declare @.mycode int
>@.mycode=sqlconnect(dsn='OMD')
>should work. It does not. I would like the proper syntax required.
>Somehow I am misinterpreting the examples in the Help files. Please excuse
>my ignorance.
>Since the code will not compile, I am not getting to the point of errors.
>Thanks for replying.
>Phil
>"Sue Hoegemeier" wrote:

Connecting to external data source

I have found several pages demonstrating this but I still cannot make it
work. I need to connect to an external data source. I have a user DSN name
d
"OMD" which does not require a username or password. My connection will be
read-only. My intent is to use SQLConnect, although I am open to any
suggestions. I have tried various methods of connecting to Access databases
,
figuring that would be easier and then I could connect to my OMD source, but
I have not been able to connect to any other data source. Any words of
encouragement would be appreciated.How exactly are you trying to connect to external data sources? Linked
servers? Openrowset? Opendatasource? Openquery?
What steps did you take to set this up with SQL Server?
What errors are you getting? What specific types of data sources are
you trying to connect to - e.g. Access, FoxPro, Oracle, Sybase, etc?
I'm not real clear on what it is you are trying to connect to from
where and what the errors are.
-Sue
On Tue, 19 Oct 2004 09:29:12 -0700, Phil T
<PhilT@.discussions.microsoft.com> wrote:

>I have found several pages demonstrating this but I still cannot make it
>work. I need to connect to an external data source. I have a user DSN nam
ed
>"OMD" which does not require a username or password. My connection will be
>read-only. My intent is to use SQLConnect, although I am open to any
>suggestions. I have tried various methods of connecting to Access database
s,
>figuring that would be easier and then I could connect to my OMD source, bu
t
>I have not been able to connect to any other data source. Any words of
>encouragement would be appreciated.|||I am trying to connect the the source any way I can.
I have tried Openrowset, openquery, sp_addlinkedserver, sqlconnect,
sqldriverconnect.
I have an ODBC connection named OMD that connects using the Transoft OMD
driver. (Although I have not successfully connected to any type of dtabase;
not even other SQL servers)
It seems to me that sqlconnect is the easiest way to connect. Since there
is no username or password required by the ODBC driver, I thought simply usi
ng
declare @.mycode int
@.mycode=sqlconnect(dsn='OMD')
should work. It does not. I would like the proper syntax required.
Somehow I am misinterpreting the examples in the Help files. Please excuse
my ignorance.
Since the code will not compile, I am not getting to the point of errors.
Thanks for replying.
Phil
"Sue Hoegemeier" wrote:

> How exactly are you trying to connect to external data sources? Linked
> servers? Openrowset? Opendatasource? Openquery?
> What steps did you take to set this up with SQL Server?
> What errors are you getting? What specific types of data sources are
> you trying to connect to - e.g. Access, FoxPro, Oracle, Sybase, etc?
> I'm not real clear on what it is you are trying to connect to from
> where and what the errors are.
> -Sue
> On Tue, 19 Oct 2004 09:29:12 -0700, Phil T
> <PhilT@.discussions.microsoft.com> wrote:
>
>|||If your code won't compile then your first issue is more of
an issue with whatever language you are using and how to
code data access routines. There is no one generic response
on how to do this with any data source and in any language.
In any case, are you trying to code this using the ODBC
APIs? If so, you need to use SQLConnect("DSN-Name") .
It would probably be easier to help you out if you could
post what language you are trying to do this in, what syntax
errors you receive, what the code is that is failing and
what examples you are trying to follow.
-Sue
On Mon, 1 Nov 2004 09:44:05 -0800, Phil T
<PhilT@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am trying to connect the the source any way I can.
>I have tried Openrowset, openquery, sp_addlinkedserver, sqlconnect,
>sqldriverconnect.
>I have an ODBC connection named OMD that connects using the Transoft OMD
>driver. (Although I have not successfully connected to any type of dtabase
;
>not even other SQL servers)
>It seems to me that sqlconnect is the easiest way to connect. Since there
>is no username or password required by the ODBC driver, I thought simply us
ing
>declare @.mycode int
>@.mycode=sqlconnect(dsn='OMD')
>should work. It does not. I would like the proper syntax required.
>Somehow I am misinterpreting the examples in the Help files. Please excuse
>my ignorance.
>Since the code will not compile, I am not getting to the point of errors.
>Thanks for replying.
>Phil
>"Sue Hoegemeier" wrote:
>

Connecting to a different stored procedure at runtime

Hello..
I am using Crystal Reports 10. Am running the report through some asp pages. The report is tied to a stored procedure at design time. Can I make the report connect to a different stored procedure at runtime? Both these stored procs have the same output in terms of columns. They differ only in the data.
Thanks,
ManishTry this
In your Application Use

CR.Database.tables(0)="SP Name"

Connecting Securely?

Hi,
I have SQL Server 2000 running on one box and IIS running on another box. I
am connecting to the SQL Server via ASP pages on the IIS box. My concern is
security -- currently I am using this kind of code to connect:
var setListings = Server.CreateObject("ADODB.Recordset");
setListings.ActiveConnection =
"Provider=SQLOLEDB.1;Password=PASSWORD;Persist Security Info=True;User
ID=USERID;Initial Catalog=tableName;Data Source=127.0.0.1"
My concern is that the username and password are being sent via plain text
from one box to the other.. Is this in fact the case? Is there another way
to make the connection? I think I could use Windows 2000 user accounts but
that would require trusted domains, etc. and neither box is a domain
controller (they are running at my ISP)
Thanks,
RichYou want to enable SSL for communication between the servers.
http://support.microsoft.com/defaul...kb;en-us;276553
-oj
http://www.rac4sql.net
"Richard Morey" <rwmorey71@.hotmail.com> wrote in message
news:ONWK0C4CEHA.2908@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have SQL Server 2000 running on one box and IIS running on another box.
I
> am connecting to the SQL Server via ASP pages on the IIS box. My concern
is
> security -- currently I am using this kind of code to connect:
> var setListings = Server.CreateObject("ADODB.Recordset");
> setListings.ActiveConnection =
> "Provider=SQLOLEDB.1;Password=PASSWORD;Persist Security Info=True;User
> ID=USERID;Initial Catalog=tableName;Data Source=127.0.0.1"
> My concern is that the username and password are being sent via plain text
> from one box to the other.. Is this in fact the case? Is there another way
> to make the connection? I think I could use Windows 2000 user accounts but
> that would require trusted domains, etc. and neither box is a domain
> controller (they are running at my ISP)
> Thanks,
> Rich
>
>|||Hi,
I have quickly glanced at the link you provided and will read it more
closely later.. Quick question -- we have SSL on the web server, not on the
SQL Server - will this still work?
Rich
"oj" <nospam_ojngo@.home.com> wrote in message
news:%230cwcK4CEHA.1128@.TK2MSFTNGP11.phx.gbl...
> You want to enable SSL for communication between the servers.
> http://support.microsoft.com/defaul...kb;en-us;276553
> --
> -oj
> http://www.rac4sql.net
>
> "Richard Morey" <rwmorey71@.hotmail.com> wrote in message
> news:ONWK0C4CEHA.2908@.TK2MSFTNGP09.phx.gbl...
box.
> I
> is
Server.CreateObject("ADODB.Recordset");
text
way
but
>|||SSL will have to be (at least) on sqlserver box for it to work.
-oj
http://www.rac4sql.net
"Richard Morey" <rwmorey71@.hotmail.com> wrote in message
news:%23fmWqq5CEHA.3344@.tk2msftngp13.phx.gbl...
> Hi,
> I have quickly glanced at the link you provided and will read it more
> closely later.. Quick question -- we have SSL on the web server, not on
the
> SQL Server - will this still work?
> Rich
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%230cwcK4CEHA.1128@.TK2MSFTNGP11.phx.gbl...
> box.
concern
> Server.CreateObject("ADODB.Recordset");
> text
> way
> but
>

Connectiing to SQL 2005 from ASP Pages

I am having difficulty connecting to SQL 2005 Express from ASP Pages.
My Web site is a mix of data driven ASP.NET 2.0 pages and some complicated
ASP pages which I have not had time to migrate. I recently copied all the my
data from SQL 2000 Server to SQL Express. My ASP.NET pages connect correctly
but when I change the connecting string in my ASP pages the pages break
without returning an error.
My working connecting string in web.config:
Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
Security=True
My working connecting string on my ASP pages:
Provider=SQLOLEDB.1;Data Source=Server2000Name;Initial
Catalog=DatabaseName;User ID=spdbuser;Password=password
Connecting strings I have tried on my ASP pages:
Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Initial
Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
Provider=SQLOLEDB.1;Data Source=.\SQLEXPRESS;Initial
Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
Security=True
I have also tried Data Source=Server2005Name\SQLEXPRESS in the three
connecting string above.
I have verified that a connection is being made from IIS in SQL Express,
using the IUSER account but the page does not serve. I have included IUSER
in the MSSQLUser group and assigned login permissions for the MSSQLUser
group to the database.
Any ideas?
Regards,
Fred Chateau
fchateauAtComcastDotNet
Hi Fred,
Check out these connection strings (they are same for express version):
http://www.connectionstrings.com/
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/
"Fred Chateau" <fchateau@.127.0.0.1> wrote in message
news:Oi%23IL0B7GHA.4304@.TK2MSFTNGP03.phx.gbl...
>I am having difficulty connecting to SQL 2005 Express from ASP Pages.
> My Web site is a mix of data driven ASP.NET 2.0 pages and some complicated
> ASP pages which I have not had time to migrate. I recently copied all the
> my data from SQL 2000 Server to SQL Express. My ASP.NET pages connect
> correctly but when I change the connecting string in my ASP pages the
> pages break without returning an error.
> My working connecting string in web.config:
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> My working connecting string on my ASP pages:
> Provider=SQLOLEDB.1;Data Source=Server2000Name;Initial
> Catalog=DatabaseName;User ID=spdbuser;Password=password
> Connecting strings I have tried on my ASP pages:
> Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Provider=SQLOLEDB.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> I have also tried Data Source=Server2005Name\SQLEXPRESS in the three
> connecting string above.
> I have verified that a connection is being made from IIS in SQL Express,
> using the IUSER account but the page does not serve. I have included IUSER
> in the MSSQLUser group and assigned login permissions for the MSSQLUser
> group to the database.
> Any ideas?
> Regards,
> Fred Chateau
> fchateauAtComcastDotNet
>
>
|||"Miha Markic [MVP C#]" <miha at rthand com> wrote...

> Hi Fred,

> Check out these connection strings (they are same for express version):
> http://www.connectionstrings.com/
It worked...
I just wanted to mention I got my original connection strings using UDL
(Windows Universal Data Link extension). I've always relied on UDL in the
past but in this scenario UDL definitely doesn't work.
Regards,
Fred Chateau
|||Probably has nothing to do with your connection strings.
1. Make sure you have an acceptable protocol to connect. Open the Config
Manager and add TCP/IP or named pipes (Express is in memory only).
2. If Express is on a different machine than the web server, turn on SQL
Browser
3. Make sure Express is set up for mixed mode. By default, it is not. I do
not have an URL, but google and you should find the command line to switch
to mixed from windows auth.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*************************************************
Think outside of the box!
*************************************************
"Fred Chateau" <fchateau@.127.0.0.1> wrote in message
news:Oi%23IL0B7GHA.4304@.TK2MSFTNGP03.phx.gbl...
>I am having difficulty connecting to SQL 2005 Express from ASP Pages.
> My Web site is a mix of data driven ASP.NET 2.0 pages and some complicated
> ASP pages which I have not had time to migrate. I recently copied all the
> my data from SQL 2000 Server to SQL Express. My ASP.NET pages connect
> correctly but when I change the connecting string in my ASP pages the
> pages break without returning an error.
> My working connecting string in web.config:
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> My working connecting string on my ASP pages:
> Provider=SQLOLEDB.1;Data Source=Server2000Name;Initial
> Catalog=DatabaseName;User ID=spdbuser;Password=password
> Connecting strings I have tried on my ASP pages:
> Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Provider=SQLOLEDB.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> I have also tried Data Source=Server2005Name\SQLEXPRESS in the three
> connecting string above.
> I have verified that a connection is being made from IIS in SQL Express,
> using the IUSER account but the page does not serve. I have included IUSER
> in the MSSQLUser group and assigned login permissions for the MSSQLUser
> group to the database.
> Any ideas?
> Regards,
> Fred Chateau
> fchateauAtComcastDotNet
>
>
|||Yep, UDL is not a good option anymore.
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/
"Fred Chateau" <fchateau@.127.0.0.1> wrote in message
news:%23JOYeTF7GHA.3644@.TK2MSFTNGP03.phx.gbl...
> "Miha Markic [MVP C#]" <miha at rthand com> wrote...
>
> It worked...
> I just wanted to mention I got my original connection strings using UDL
> (Windows Universal Data Link extension). I've always relied on UDL in the
> past but in this scenario UDL definitely doesn't work.
> Regards,
> Fred Chateau
>
|||"Cowboy (Gregory A. Beamer)" wrote ...

> Probably has nothing to do with your connection strings.
It _was_ the connection string, Cowboy.
ASP.NET 2.0 --> Data Source=.\SQLEXPRESS;Integrated Security=True
ASP --> Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Integrated
Security=SSPI
"Integrated Security=True" does not work in ASP.
Regards,
Fred Chateau
fchateauAtComcastDotNet

Connectiing to SQL 2005 from ASP Pages

I am having difficulty connecting to SQL 2005 Express from ASP Pages.
My Web site is a mix of data driven ASP.NET 2.0 pages and some complicated
ASP pages which I have not had time to migrate. I recently copied all the my
data from SQL 2000 Server to SQL Express. My ASP.NET pages connect correctly
but when I change the connecting string in my ASP pages the pages break
without returning an error.
My working connecting string in web.config:
Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
Security=True
My working connecting string on my ASP pages:
Provider=SQLOLEDB.1;Data Source=Server2000Name;Initial
Catalog=DatabaseName;User ID=spdbuser;Password=password
Connecting strings I have tried on my ASP pages:
Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Initial
Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
Provider=SQLOLEDB.1;Data Source=.\SQLEXPRESS;Initial
Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
Security=True
I have also tried Data Source=Server2005Name\SQLEXPRESS in the three
connecting string above.
I have verified that a connection is being made from IIS in SQL Express,
using the IUSER account but the page does not serve. I have included IUSER
in the MSSQLUser group and assigned login permissions for the MSSQLUser
group to the database.
Any ideas?
Regards,
Fred Chateau
fchateauAtComcastDotNetHi Fred,
Check out these connection strings (they are same for express version):
http://www.connectionstrings.com/
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/
"Fred Chateau" <fchateau@.127.0.0.1> wrote in message
news:Oi%23IL0B7GHA.4304@.TK2MSFTNGP03.phx.gbl...
>I am having difficulty connecting to SQL 2005 Express from ASP Pages.
> My Web site is a mix of data driven ASP.NET 2.0 pages and some complicated
> ASP pages which I have not had time to migrate. I recently copied all the
> my data from SQL 2000 Server to SQL Express. My ASP.NET pages connect
> correctly but when I change the connecting string in my ASP pages the
> pages break without returning an error.
> My working connecting string in web.config:
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> My working connecting string on my ASP pages:
> Provider=SQLOLEDB.1;Data Source=Server2000Name;Initial
> Catalog=DatabaseName;User ID=spdbuser;Password=password
> Connecting strings I have tried on my ASP pages:
> Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Provider=SQLOLEDB.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> I have also tried Data Source=Server2005Name\SQLEXPRESS in the three
> connecting string above.
> I have verified that a connection is being made from IIS in SQL Express,
> using the IUSER account but the page does not serve. I have included IUSER
> in the MSSQLUser group and assigned login permissions for the MSSQLUser
> group to the database.
> Any ideas?
> Regards,
> Fred Chateau
> fchateauAtComcastDotNet
>
>|||"Miha Markic [MVP C#]" <miha at rthand com> wrote...

> Hi Fred,

> Check out these connection strings (they are same for express version):
> http://www.connectionstrings.com/
It worked...
I just wanted to mention I got my original connection strings using UDL
(Windows Universal Data Link extension). I've always relied on UDL in the
past but in this scenario UDL definitely doesn't work.
Regards,
Fred Chateau|||Probably has nothing to do with your connection strings.
1. Make sure you have an acceptable protocol to connect. Open the Config
Manager and add TCP/IP or named pipes (Express is in memory only).
2. If Express is on a different machine than the web server, turn on SQL
Browser
3. Make sure Express is set up for mixed mode. By default, it is not. I do
not have an URL, but google and you should find the command line to switch
to mixed from windows auth.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
****************************************
*********
Think outside of the box!
****************************************
*********
"Fred Chateau" <fchateau@.127.0.0.1> wrote in message
news:Oi%23IL0B7GHA.4304@.TK2MSFTNGP03.phx.gbl...
>I am having difficulty connecting to SQL 2005 Express from ASP Pages.
> My Web site is a mix of data driven ASP.NET 2.0 pages and some complicated
> ASP pages which I have not had time to migrate. I recently copied all the
> my data from SQL 2000 Server to SQL Express. My ASP.NET pages connect
> correctly but when I change the connecting string in my ASP pages the
> pages break without returning an error.
> My working connecting string in web.config:
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> My working connecting string on my ASP pages:
> Provider=SQLOLEDB.1;Data Source=Server2000Name;Initial
> Catalog=DatabaseName;User ID=spdbuser;Password=password
> Connecting strings I have tried on my ASP pages:
> Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Provider=SQLOLEDB.1;Data Source=.\SQLEXPRESS;Initial
> Catalog=DatabaseName;Integrated Security=SSPI;Persist Security Info=False
> Data Source=.\SQLEXPRESS;Initial Catalog=DatabaseName;Integrated
> Security=True
> I have also tried Data Source=Server2005Name\SQLEXPRESS in the three
> connecting string above.
> I have verified that a connection is being made from IIS in SQL Express,
> using the IUSER account but the page does not serve. I have included IUSER
> in the MSSQLUser group and assigned login permissions for the MSSQLUser
> group to the database.
> Any ideas?
> Regards,
> Fred Chateau
> fchateauAtComcastDotNet
>
>|||Yep, UDL is not a good option anymore.
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/
"Fred Chateau" <fchateau@.127.0.0.1> wrote in message
news:%23JOYeTF7GHA.3644@.TK2MSFTNGP03.phx.gbl...
> "Miha Markic [MVP C#]" <miha at rthand com> wrote...
>
>
> It worked...
> I just wanted to mention I got my original connection strings using UDL
> (Windows Universal Data Link extension). I've always relied on UDL in the
> past but in this scenario UDL definitely doesn't work.
> Regards,
> Fred Chateau
>|||"Cowboy (Gregory A. Beamer)" wrote ...

> Probably has nothing to do with your connection strings.
It _was_ the connection string, Cowboy.
ASP.NET 2.0 --> Data Source=.\SQLEXPRESS;Integrated Security=True
ASP --> Provider=SQLNCLI.1;Data Source=.\SQLEXPRESS;Integrated
Security=SSPI
"Integrated Security=True" does not work in ASP.
--
Regards,
Fred Chateau
fchateauAtComcastDotNet