Sorry, I don't have a sample I can send, but in concept it's very simple.
You write an active-X DLL that does all database access. The user interface has no, repeat NO, database code in it -- it only calls the middle layer.
So if you have an employee table, you'd write an CEmployee class in an Employee VB DLL project. In this class, you'd have Create, Remove, Update, and Delete methods (known in the industry as CRUD, believe it or not).
You can then write any user front-end you want on top of this DLL -- Web/ASP, Client-Server, whatever. All the front end does is call the DLL, who does most of the work for you.
A big benefit of this is that all your business logic is in one place. So you can add protection from unauthorized persons from updating employee salary info, for example. These rules would then be applied no matter what client was used to connect to the middleware.
Chip H.