Thank you. I was thinking the same approach too. However, I have places where some objects are instantiated in code; therefore, at run time I may still get errors. So, thoroughly testing is still required.
>I would remove depreciated class and follow errors generated
>
>>
>>I am begging an "in-house" project of removing all classes and classlibs that I don't think are used in the application (the key is 'I don't think' because I am not 100% sure). I will illustrate one here:
>>I have a classlib 'dbf_main.vcx' with a class 'adding_new_record'. There are other classlibs that have a class of the same name, 'adding_new_record'. I have tried GoFish but it returns many places where name 'adding_new_record' is used. Would the only reasonable approach be to go to each place where this name is used? Then, commenting/changing them, one at a time? Any other suggestions?
>>
>>TIA
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham