>I'm hearing LOGICAL 3-tier design quite a lot, what is the main difference with LOGICAL 3-tier, is that because you are talking to the DB directly?
>

Hi Kev,

Logical 3-tier is more a development philosophy in which the functional parts of your design are separated based on what they do. If they interact with the database, they're grouped in the data tier, if they deal with business logic they're in another tier, and if they relate to UI they're in the interface layer.

For example, in the framework I use (Mere Mortals) the design is made in such a way that you can "drop" business objects on your forms. Whatever process requires touching data is controled at the business object level.

Also, I could have a "managing" object control the work of several business objects.

The app is still a single executable, but when I need to make modifications to my design, I know exactly where to look for everything... this also takes care of the "where's the code" syndrome, so common when you can place code pretty much anywhere you want.

Alex