>There is no right or wrong way. Stonefield starts all their classes with sf. However, if you look at Codebook and COMCodebook, they use c for the company layer, then i for an intermediate layer and a for each application layer.
>
>
>>To All,
>>
>>Every now and then I have a 'holy war' with new colleagues (I hop a lot) about the naming of classlibs. E.g., should the highest/base classlib be named after the 'owning' company and should we only use a subclass of that classlib in a specific application, and name the subclassed lib after the application? Like:
>>
>>

>>   abcBase.vcx       Your company ABC?
>>   abcReporting.vcx  Based on base classes in abcBase.vcx?
>>   *
>>   defBase.vcx       Subclass of abcBase.vcx for your customer 'company DEF'?
>>   defReporting.vcx  Subclass of abcReporting.vcx for your customer 'company DEF'?
>>   *
>>   ghiBase.vcx       Subclass of defBase.vcx for your customer's application GHI?
>>   ghiReporting.vcx  Subclass of defReporting.vcx for your customer's application GHI?
>>

>>I don't want to start a holy war, but I'm quite interested in your naming conventions!

Did someone say holy war? I love a good holy war! Insofar as naming conventions for classlibs are concerned, I try to maked them consistent and meaningful. The only naming conventions that I recommend that you always adhere to are variable names and field names. By the way the "a" layer in Codebook can be broken into several application specific class libraries. This is where I start naming things according to their functionality, such as: invobjs for invoice\ objects, or custobjs for customer objects.