Unknown Error

[mthrawn]

I've been locked out of a form after making a few minor alterations. The changes involved mainly client side and going from this kind of format (for various reasons)

function btnConfirm_onclick()
{
....
}

to

function btnConfirm_onclick()
{
doIt();
}

function doIt()
{
......
}

As you can see, no recordset changes, in fact no significant changes at all. The error I get is noted below.

Error Type:
Microsoft Cursor Engine (0x80040E21)
Multiple-step operation generated errors. Check each status value.
/SQS_new/_ScriptLibrary/Recordset.ASP, line 424


I've not got a clue what it means and the MS knowledge base was as useless as ever...can anyone help?

Matt

All the people in all the world and I had to be me.

 

[foxbox]

I see several articles pointing to problems with AddNew.
more info on this page...

http://support.microsoft.com/support/kb/articles/Q247/2/02.asp

br
Gerard

 

[mthrawn]

Well thanks for your reply, but it turned out the error was down to me not setting a boolean flag properly, and was (as I suspected) nothing to do with any of the recordsets. If the error message hadn't been pointing my debugging focus in completely the wrong direction it would have taken me about ten minutes to solve, as it was it took two days. I would send a mail to Microsoft to make a point about this but hey, what would be the point?

Matt

All the people in all the world and I had to be me.

 

[MauricioB]

Hi. I have the same problem but i HAVEN'T solve it yet. I can see thet you could so please if you can give me some gidlines that will help me to solve this problem, please do it. thanks

 

[MauricioB]

Hey I have the same problem but i haven't just find the answer. i can see that you already have, so if you can give me some guidelines in oprder to solve this problem, I will appresiante it. Thaks

 

[MerlinB]

Yes, the multi-step error is a bit of a pain. In this case it happened because you tried to put an in-appropriate value into a database column.

You could try turning on ODBC trace (as the SQL is hidden from you) or SQLServer trace so you can 'see' the SQL at fault. You could try pasting the SQL into the 'Query Analyser' (or whatever sql tool you have) and trying to execute it manually. The error returned in these tools tend to be more meaningful!

http://www.websitedesign.co.uk

http://www.zentext.com

(Content Management)