>Peter,
>
>Thanks. I've downloaded your tool and will take a look at it as soon as I get a chance ...
>
>I'm also going to write a VFP program that will scan all the meta data tables for all forms in a project and will print a report showing what classlibs are used in that project.
>
>This will help detect whenever an incorrect classlib was used, and, more importantly, which component is the culprit.
>
>I will make this program available to anyone who wants it.
That is an ambitious project. However, isn't it perhaps a little bit too ambitious? As I suggested, you already do have that list of used classes. They are all listed in the Classes tab of the Project Manager, after a rebuild.
Whenever you encounter an 'incorrect' classlib over there, you can contact your developers and 'ask' which object on which form might be the culprit. The advantage of this strategy is that your developers develop a sense of awareness and attention that will prevent most abuse in future.
I am of opinion that your tool may be too 'developerfriendly'.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
