>>>Maybe not relevant to your case, but you might find the C5s are being caused by exiting method from within a with/endwith construct.
>>>
>>
>>I think that's the reason Koen wants to change.
>
>But that is not a particularly good reason for changing everything you must to remove the WITH/ENDWITH. We redid our whole framework just making sure procedures had properly been followed that there was only one exit point from a method and that it came at the end, outside of blocks. Exit state controlled by variables. Much easier and IMO better coding technique.
>

I re-factored recently myself one complex procedure with multiple complex functions to ensure one exit point in every function. But there are too many procedures and I can not refactor each of them.