On Fri, Nov 26, 2010 at 9:52 AM, Processor Devil <[email protected]> wrote: > Why not? Now I don't want to hear anything about best practices, I also had > times when using variables like tblSomething, strSomething, fltSomething and > it still worked. Is there any other problem in that than simply screwing > some programmer's ethics? -------------------------------------------
Data objects don't need to present object types in name. Sorry but Customers or tblCustomers is the same thing. Why OVERWHELM intellisense by stuffing every friging TABLE together? Sorry but it is just sad design from my POV. YMMV. ;-> In a GUI having all txtBoxes together is good for ease of finding the one you are looking for and you don't have too many to deal with, I hope. Now putting the data type for each column really can tweak me as very poor design. vcCustomerName, dtInvoiceDate, intInvoiceNumber. Why waste the letters? Is there any benefit that you receive? I am a firm believer of KISS naming when we live in a strict type data environment. -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell
