Ok, I found it! I somehow ended up "Trimming" one of the variables that was being passed to the stored procedure. Hence I was sending an empty string rather than a string with some spaces. Rather than Oracle returning an error the entire application would crash completely. Figured I'd place this out here in case anyone else runs into this problem.

George

---

>This has been working fine until a couple of hours ago. I know there was a bit of a thread on this in the last week or so and went back to read it but never saw a real solution. If I missed it please just point me in the right direction. Otherwise, any help would be great because I am dead in the water right now.
>
>I am basically calling an Oracle stored procedure to validate a login/password and return a validity code. The call looks like this:
>
>

>ResultCode=SQLEXEC(oUserInfo.ConnHandle, ;
>        "{CALL pCheckLogin (?lcLogin, ?lcPassword, ?@lcUserName, ?@lcSource, ?@lcAccessLevel, ;
>               ?@liRetVal)}")
>

>
>For some reason as soon as it hits this line I get the C...5 error. If I copy this code and put it into a temp file and run the same thing, everything works fine. All of the parameters being passed are correct and this is a valid connection handle.
>
>I can't find much of anything in TechNet or any other MS resources. Any ideas?
>
>Thanks,
>George