Bob,
I think I know what may be happening. I believe that you must use a User ID
and Password to connect to the DB in ASP,VBScript. I believe this because
every connection string that uses a trusted connection works fine in VB 6.0.
If I try to use a connection string in VB 6.0 that uses User ID and PassWord
I get the following error:
(Login failed for user '<LoginName>'. Reason: Not associated with a trusted
SQL Server connection)
I have tried every suggestion from MS website on how to setup a User ID and
Password that is associated with a trusted SQL Server connection but cannot
make one work. I have SQL 2005 setup in authentication mode = SQL Server
and Windows
Sincerly,
Bob Hiller
"Bob Barrows [MVP]" <reb01501@NOyahoo.SPAMcom> wrote in message
news:%236L%2323QSGHA.4384@tk2msftngp13.phx.gbl...[color=blue]
> Nobody can help you if you just throw up your hands instead of describing
> your symptoms.
>
>
>
>
>
> Bob and Sharon Hiller wrote:[color=green]
>> I am starting to think that there is no way to connect to SQL 2005
>> with VBScript. I have tried 25 different suggestions from news groups
>> and forums and none have worked. The only thing that seems to work is
>> report services using .net and we are not going to change every page
>> we have. I think we will just go back to SQL 2000 where everything
>> worked fine.
>>
>> Thanks for the help.
>>
>> Bob Hiller
>>
>>
>> "Bob Barrows [MVP]" <reb01501@NOyahoo.SPAMcom> wrote in message
>> news:ObyyS0PSGHA.224@TK2MSFTNGP10.phx.gbl...[color=darkred]
>>> Bob and Sharon Hiller wrote:
>>>> Bob,
>>>> After
>>>> intRecordCount = adoRecordset.RecordCount
>>>>
>>> With a default server-side, forward-only cursor, Recordcount will
>>> always contain -1.
>>>
http://www.aspfaq.com/show.asp?id=2193
>>> As this article says, there are better ways to count the records
>>> returned by
>>> a query.
>>>
>>>>
>>>> I also tried:
>>>> intRowsCount = adoRecordset.GetRows
>>>
>>> Mike addressed this one.
>>>>
>>>> Looking at the link you sent, it appears that I would need to
>>>> totally reconfigure the SQL server to use that method.
>>>
>>> Why? Where does that article say anything about reconfiguring SQL
>>> Server if
>>> you don't have to? Simply change your connection string to the one he
>>> suggests using for integrated (Windows) security. Here, let me show
>>> you:
>>>
>>>>>> Set adoConnection = server.CreateObject("ADODB.Connection")
>>>>>> Set adoRecordset = server.CreateObject("ADODB.Recordset")
>>>>>> adoConnection.ConnectionString = "Provider=MSDASQL.1;" _
>>>>>> & "Persist Security Info=False;" _
>>>>>> & "Extended Properties=Description=Large Pump Data Source;" _
>>>>>> & "DRIVER=SQL Server;SERVER=LPDATASYSTEM\PL3LP;" _
>>>>>> & "APP=Microsoft Data Access Components;" _
>>>>>> & "WSID=LPDATASYSTEM;DATABASE=LargePump;" _
>>>>>> & "Trusted_Connection=Yes;Initial Catalog=LargePump"
>>>>>
>>> adoConnection.ConnectionString = "Provider=SQLOLEDB;" _
>>> & "Persist Security Info=False;" _
>>> & "Data Source=LPDATASYSTEM\PL3LP;" _
>>> & "Application Name=Microsoft Data Access Components;" _
>>> & "Integrated Security=SSP1;Initial Catalog=LargePump"
>>>
>>> 'I would suggest setting the Application Name to a more specific name
>>> rather
>>> than the generic "Microsoft ... ". This will allow debugging using
>>> SQL Profiler to be easier (you can set up a trace using a filter to
>>> display only
>>> a specific application).
>>>
>>> Bob Barrows
>>> --
>>> Microsoft MVP -- ASP/ASP.NET
>>> Please reply to the newsgroup. The email account listed in my From
>>> header is my spam trap, so I don't check it very often. You will get
>>> a quicker response by posting to the newsgroup.[/color][/color]
>
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.
>
>[/color]
