Re: Here's a rather broad question...

I've finally had a few minutes to toy with this some more...

The data route should be

ASP code & pages <--> ADO <---> OLEDB SQLServer Native Provider <---> SQL
Server 2005

Had you been using ODBC it is more complicated

Agreed; in this day and age, ODBC is to be avoided, especially if, like me,
you're trying to do this through a 64-bit environment. Has anyone even
bothered creating 64-bit ODBC drivers?

Beef up the security once you have a working prototype.

Well, here's, generally, what I did:

- nuked both SQL Server 2005 and IIS
- reinstalled them both
- used your connection string ("Provider=sqloledb;Data
Source=yourserver;Initial Catalogue=yourdatabase;Integrated Security=SSPI")
with blank username/password
- (note that I had to change that to Initial Catalog--without the
terminating 'ue', or it would complain it's not a valid element)
- it complained the IIS user (MyMachineName\IUSR_MyMachineName) didn't have
access rights to my database, so I changed IIS's anonymous user to my own
account

Bingo, that worked. Now, of course, I don't wanna let the anonymous user
run as myself, as I run as admin on that box. Switching IIS's anonymous
user back to IUSR_MyMachineName, the page once again complained that this
user doesn't have access to the database. Now, my next problem is, how do I
tell SQL Server that this user should have read rights to that database? I
don't have it in front of me right now so I can't recall the exact steps,
but when I try to create a new SQL Server user, if I try to browse through
existing users, that account isn't listed--because, I'm assuming, one is for
SQL Server authentication, while I'm actually trying to use Windows
authentication...

I'm assuming it makes more sense then to use SQL Server authentication, and
specify this user name/password in my connection string--and this is where
after messing so much with these settings I got in a state where nothing
worked...

To put it bluntly, where would you go from here?


.

Relevant Pages

  • Re: Need ODBCDirect-ion
    ... Just as a side note, ODBC, or so called "jet" direct is simply a way to ... You need experience with sql server. ... "Upsizing to Microsoft SQL Server" White Paper Available in Download ... Choosing Database Tools White Paper Available in Download Cente ...
    (microsoft.public.access.modulesdaovba)
  • Re: Supporting a variety of database types in an app?
    ... Ralph, thank you for your insightful response. ... To get experience with MS SQL Server and client/server development. ... My rationale for using a file-based database location/selection method: ... ODBC API, but modified it to enhance performance). ...
    (microsoft.public.vb.database)
  • Re: Trusted Connection
    ... HOWEVER, for one of my users, I will create an ODBC DSN ... for my test database ON THEIR COMPUTER, ... So, when I set up the ODBC DSN connection for this user, ... >> Our SQL Server was set up NOT by me, ...
    (microsoft.public.sqlserver.security)
  • Re: Performance of ODBC
    ... ODBC / MDB is a waste of time. ... Usiing Access front-end to connection a back end through ... the database via ODBC with the Jet database engine. ... that Access is the front end, and the SQL server is the back end. ...
    (microsoft.public.access.adp.sqlserver)
  • SQL Server ODBC Driver Ignores Authentication Setting
    ... set their ODBC connections with SQL Server Authentication, ... Microsoft Data Access Components 2.6 RTM, ... authentication to log into the database. ...
    (microsoft.public.sqlserver.security)