Some people don't seem to understand why visual component prefixes are used.... lmddckpnlSales has advsbtnFilter and lmdfrmdsplySaleEdit on it. If we have to have them can they at least be shorter than the name of the component? Really, I don't care that the button in question is a TMS one, or that it's the "s" variant, I just care that it's a button. And most of the time I care more about what other controls it's with, or what it's for, than I care about what sort of control it is. I'm a fan of the "purpose first" naming so things sort together: SaleDiscountButton: TAMSFunkyGraphicButton; SaleDiscountPercentageEdit: TJEDIPercentNumericEdit; SaleDiscountFixedAmountEdit: TFredsFunControlsCurrencyEdit; SaleDiscountDescriptionEdit: TOverdesignedEditControl; That way when you see SaleDiscountDescriptionEditOnMenuPopup(nil); in code you're not in any doubt as to what it is, and you can probably guess what the method does. But advgr...