sorry, cje. I made the change and it still crashes. Same error, "Operation is not allowed when the object is closed".

set param1 = cmd.createparameter("@Start", adDBDate, adParamInput, ,CDate(RangeA.value))

cmd.Parameters.Append param1

set param2 =...

Yes, I did try both of your suggestion, Lisa.

1) Try this way and it made no different, gave me the same error code.

Set rst = cmd.Execute

If Not rst.BOF() Then ...

2)...

I have tried the above suggestion suggestions, none works for me.

Below is my new sub procedure code:

Sub GetData()

Dim RangeA As Range

Dim RangeB As Range

Set RangeA = Worksheets("CS").Range("B3")

Set RangeB = Worksheets("CS").Range("E3")

Dim...

Thank you for the reply, cje.

On my stored procedure, I do have the SET NOCOUNT at the top. Like you said, it ran perfectly find in QA. Below is how...

yes, I did search the registry. Nothing associated with MSSQL / SQL / Microsoft SQL was found. For the instance / working directory, I already removed them manually after uninstalled...

All the reg entries in that article do not exist on that XP machine. I was able to dup the issue on another XP machine. I used the same procedure...