Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Gold Super Contributor
Posts: 3,087
Registered: ‎03-19-2009

Ever get one of those "multi-step" errors?

[ Edited ]

The unfortunate thing about this error is it CAN be prevented.


However, 99% of the time it is pointing to a place (at least in the Windows Client) in the code/script where a recordset is being written back to the db. ... and 99% of the time it has to do with "ms-matched" data... and it is usually a "string too long" for the field in question.


Here's something you can run in SQL (against your db) that will show you the types/length of fields in tables:



  I commented out the "Where clause" above but you can run it with the appropriate table name to return only that table info.


Oh yes - how to prevent?.. just add the appropriate "code checks" for string length and/or set the property (MaxLength) to a specific length on DATA_BOUND control(s).


RJ Ledger - +1 603.369.3047 x101

".. Innovators in Mobility - Experts in Workflow Automation..." - blog: