>>It's not that simple as it sounds. Doing it in reverse way as you're suggesting will take much longer to find the problem comparing with my idea to start fresh.
>
>Actually, few weeks ago someone here suggested a faster way: remove objects in groups, by class. First remove all the textboxes, then combos, etc. Also, you may comment out all the code and then uncomment gradually.
>
>There's no sure-fire way to know... unless you could be more specific about the actual error.

Yesterday at night I think I came up to the good scenario I'm going to try. I'm going to copy current broken class to a safe place. Then will get the latest working version of the class from the Visual Source Safe. Then apply the changes I made yesterday (I just changed two methods and added definition of another method but hadn't coded it yet). The method I added yesterday should actually belong to another class, I think.