Edward,

A project I worked on a couple of years ago used a layered architecture. It split the vaious elements like business logic, data validation into various levels. This approach is typically frowned upon by designers as it goes against the encapsulation characteristic of an object having data + code. In this type of design, some of the objects just contain code. However, the design does allow you the benefit of using a traditional database and all the advantages that gives, as well as the advantages of having an object oriented application: reduced complication, better code reuse etc. One other big advantage of the architecture was that communication was improved amonst developers in the team, futhermore the developers could quickly track down and identify problems - even if it they weren't the original author.

Since working on the project I've utilised the architecture in all my personal projects and taken it one step further and developed generators to create most of the code for me.

I don't know about videos, but you could get training in this type of architecture by consultants from Rational, Valtech or even myself :).

I hope this is of some help

Mace