I was getting this error in my application when running a stored procedure: "ElevateDB Error #1011: An error occurred with the parameter PUsername (A conversion error occurred with the value John)".  

It is simply a string being assigned to a varchar property.

I ran the stored procedure directly and no error.  

I checked the Params property for the stored procedure component and all was correct.  I then deleted all of the parameters in the Params property so it would re-create them.  Ran the application again and it worked fine.  No error.

So it seems that somehow the parameters in the Params property of the stored procedure component get messed up, even though they look fine.  I have had this happen recently on 3 other occasions with the parameters of other stored procedures.  The problem is I never know when this problem is going to turn up and it's been happening to stored procedure components that haven't been touched for a while.

Elevate DB 2.21 Build 1.

Has anyone else experienced this?

= Steve

Forgot to mention: RAD Studio XE7 Professional.

I think this may be more of a problem with Delphi than EDB.

= Steve

Steve,

<< I think this may be more of a problem with Delphi than EDB. >>

The Delphi form/data module is where the Params are *stored*, so there could be a difference between the form/data module stored parameters and the actual stored procedure.

Are you modifying the call parameters for your stored procedures on a regular basis ? If so, then I would probably think that this is a case of a simple mismatch between the two.

If this happens again, email me the form or data module along with the stored procedure DDL CREATE statement (grab using EDB Manager) and I'll take a look and see what the discrepancy is.

Tim Young
Elevate Software
www.elevatesoft.com

<< The Delphi form/data module is where the Params are *stored*, so there could be a difference between the form/data module stored parameters and the actual stored procedure.

Are you modifying the call parameters for your stored procedures on a regular basis ? If so, then I would probably think that this is a case of a simple mismatch between the two.

If this happens again, email me the form or data module along with the stored procedure DDL CREATE statement (grab using EDB Manager) and I'll take a look and see what the discrepancy is.  >>

I have modified some parameters a few times for a couple of stored procedures.  I'll let you know if it happens again.