I am dealing with several Visual Basic 6 programs that the guy who wrote it went out of his way to make it difficult to follow thinking he would have a job forever. In a sense it worked, most others, even though they are very well versed in VB, throw there hands up in disgust and run away. I however do not run from a challange.
What has helped is to map the program by putting Debug.Print statments in every module so we have a roadmap of where the program goes. I found a work around I am not really happy with, I put symbols like #$%^ in front of and behind ObjMember.name in order to do a search for #$%^ and replace everyone with a ".
I will try what you have above but I ran into another problem. Debug.Print ObjMember.name is inserted into the module but if the person who wrote the module did somthing like this:
Private Sub MySub(Parameter1, _
Paremeter2, _
Parameter3)
The statment is inserted like this:
Private Sub MySub(Parameter1, _
Debug.Print ObjMember.Name
Paremeter2, _
Parameter3)
This of course will cause an error. I get the code line where the module begins and add 1 to it. This works well except for the situation above. Any ideas?