If I try to start a debug on a stored procedure which has a varbinary(max) parameter, I got the following error:
“The selected object type is not valid for debugging.
Column Type doesn’t exist”
when I click on “OK”,then I have a question about manual change on startup code and the the following error:
“System.NullReferenceException
Object reference not set to an instance of an object.
Stack Trace:
at Quest.Toad.Editor.EditorControl.set_IsModified(Boolean value)
at Quest.Toad.Debugger.DebugStartControl.RevokeEdit()”
Is this a limitation of Toad? A bug?
If not corrected already, Is there any plan about when it will be corrected?
Thank you for your answer.
Can you tell me more about that bug?
Also it seems that is also affecting some stored procedure which do not use varbinary(max) variables.
Can you tell me what are the limitations for debuging stored procedures please?
How can I follow the life cycle of that bug?
What are the previsions to solve it?
We were thinking about buying a DEV version (with benchmark), but I have to say that handling those types of variables and being able to debug some basic stored procedures is a “must have”.