Another trick is to use the same field twice...

CREATE PROCEDURE usp_person_details

@race varchar(30) = null,

@lastname varchar(30) = null,

@anotherfield varchar(30) = null

AS

SELECT * FROM person_details

WHERE

race = COALESCE(@race, race)

AND

lastname = COALESCE(@lastname, lastname)

AND

anotherfield...

Just an idea, if you're not absolutely sure the password is being reset to something else, then:

-obviously you have another login you can use (when you reset the sa pwd)

-so...

Once you get the connection string working, you can totally skip the command object. However, there are times you need it so if you are in a learnng exercise, great....

'This approach uses the stored proc as a connection method.

Dim Conn ' As ADODB.Connection

Set conn = Server.CreateObject("ADODB.Connection")

conn.Open "Driver={SQL Server};Server=xxx.xxx.xxx.xxx;Database=WOSC"

'You probably should really edit these Request variables first for validity

conn.prAdditem Request("Firstname"), Request("Lastname")...

(This is my first post here).

I wanted to get in this thread because I have had both success and failure doing the same thing.

I have two remote clients. On each...