Wednesday, February 15, 2006

Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

I worked a long time on this error with the application I am developing in ASP. My research today has shown that this is often a datatype problem. If the value that is filled in the form is not the same as that has been defined in the database, you get this error. For example, if you are passing a null value to a field that doesn't accept them (DATETIME field) or passing an value to a Boolean field etc.

For more information on this error, click here

4 comments:

Bala said...

not all the time...coz i get this error now...and have passed all the values correctly but i still get this error. I say i have passed everything correctly because, I cross-check it with the sql profiler and the command and the parameters that come in work well when executed. But for some reason i get this error... Any other possibilities as to why i get this error...also i have checked other things like removing persist security info...


thanks for any help in advance...

Anonymous said...

Great work!
[url=http://lpywifor.com/rkqw/jvny.html]My homepage[/url] | [url=http://hrratmdv.com/obdg/vjdn.html]Cool site[/url]

Anonymous said...

Nice site!
My homepage | Please visit

Anonymous said...

Thank you!
http://lpywifor.com/rkqw/jvny.html | http://yskiegqz.com/vjlq/mbvf.html

INSERT EXEC failed because the stored procedure altered the schema of the target table.

This morning I was trying to call a stored procedure and insert the results in a temp table using the following code  -- create table #...