Ben wrote:
> Thanks for the information, I finally got it to work.
>
> Bob:
> I printed out the strSQL statement and realized that I was
> assigning my values incorrectly, after fixing that it
> worked perfectly.
>
> Ray:
> What does the 129 in this line mean?
>> adoCon.Execute strSQL,,129
>
Since I'm here I'll answer for Ray:
129 is the combination of two values: 1 and 128
1 = adCmdText. It tells ADO that you want it to execute a sql statment
contained in a string. Always supply this argument. Don't make ADO guess
what the command type is:
a) It wastes programming cycles
b) It may (rarely) guess wrong
128 = adExecuteNoRecords This tells ADO that you do not expect to get any
records back from the query you are executing, so it will not waste
resources and processing cycles creating a recordset behind the scenes to
receive a non-existent resultset.
If you are not using Visual Studio, you can find the ADO documentation at
msdn:
http://msdn.microsoft.com/library/en...dooverview.asp
In particular, the Execute command is explained here:
http://msdn.microsoft.com/library/en...cnnexecute.asp
HTH,
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.