You might want to add that the syntax:

cmdMyCommand.Parameters("@LastName") = strLastName

that works just fine under ADO

doesn't seem to work under ADO.Net.

Sprocs don't seem to know anything about their parameters until execution. I guess it makes sense when one considers the basic idea behind ADO.Net is to do away with stateful database interactions.

This change was the cause of some consternation here, as disappearance of the the old syntax does not seem to be documented anywhere.

Brian Begy

Chicago Data Solutions