When you rebuild the Project, the classlib of a recently dropped class will be pulled in the Project. The Classes tab will gonna show you its name. Therefore, this tab can be used to check whether or not only legitimate classlibs have been used.

I assume (or advice) that you have a scheme for naming classlibs.

Very recently I built a developer-tool for naming classes (not classlibs). It may be of further help. Here is the link: http://www.viafox.nl/downloads/NewClass_beta2.zip


>A frequently reoccurring problem in my company has me looking for a better way.
>
>What is happening is that very often one of my programmers will forget to click on the VFP Class Library (i.e. View Classes) icon to add the correct Class Library to the VFP component toolbar. He/she will then proceed to add components to a form from a foreign project.
>
>Since we have several VFP projects going on at any given time, we often find ourselves in the situation where components get added to a form that were subclassed in another project. This requires going into the Meta data for the form and manually changing the ClassLoc and Class fields in the Meta data table.
>
>I was looking for a way to be able to possibly detect this at design time, maybe by putting some code into the Form subclass that could possibly programatically evaluate the Meta data when a new component is added to the form and disallow the addition of the component if it is not from the correct Class Library. But I couldn't see any way of accomplishing this ....
>
>Anyone have a solution to this problem?
>
>Thanks,
>
>-Steve