I thought you were saying the way I was creating my Connection, Command and RecordSet objects were causing my problems. I can produce this same problem in VB.NET, VB and Visual Foxpro 9 using ADODB version 2.8. Kurt's response to my problem seemed to fix my problem.

THE "SET NOCOUNT ON" seemed to allow the rest of my Stored Procedure to fire after my Update command, where if did not include it, it would stop at that point.

Thanks for you help with this matter.