Mike,

I inherited this mess............ ugh.............

I agree, having only one class per library will cut down on this big steaming pile of crap that happens when the class library goes belly up for some reason.

I also see Craig's point too......... having properly named and utilized libraries make it far easier to find a class in particular, IF you don't quite remember the exact name for it..... FORM classes for the RX related forms go in the forms_rx library.

Of course, a hap-hazardly thrown together class library system will be just as hard to use to find classes as having one class per library

Both systems have their plus's and minus's............. you will have to clearly plan ahead in either way and stick to a system that will work best for you.

Tommy

>I'm seemingly the biggest proponent of having only one class in a classlib. That is exactly the same as saying having only one screen in an scx. I just name the class and the classlib the same.
>
>>Hey Fernando!
>>
>>The FoxBin2Prg worked like a CHAMP !!! I had to use the 2nd method to get rid of all the duplicates ( I had over 3000 records in the class library to start with, then I had only 2000 left after cleaning! What a mess!! ).
>>
>>There is another discussion in Coding, Syntax and Commands called " Which class is used if 2 classes have same name in class library"..... sounds like they might need some help !!! You might want to chime in there too !!
>>
>>Thanks again for the help !!
>>