>Seconding Craigs worries about what functionality to put into which layer - esp. after the thread of firing a table lookup out of a control refresh.
>Those tiny shortcuts add up over time - if you really think about selling your SW you should clean such things up instead of adding more small warts -
>even if often the "correct" architecture will add more code / slowness to the app then doing it dirty.
>Build stable and refactor / optimize a layer begins to eat into the performance ;-))
>

Good advice...