>
>>If I'm working with ADO I find it very confusing being in a 3-tier app, if I had the UI working with ADO recordsets, that are based on tables in the data-tier, isn't that creating a direct-link between the UI and the Data? Or have I got this method of working wrong?
>
>I don't know how sophisticated this is, but in my mind ADO recordsets are a data layer, sorta. As are stored procedures. If a UI talks to an ADO recordset then that's a client/server, or 2 tier model, right? You're bypassing the business layer. But you haven't coupled data with the UI. (The ADO is inbetween.)

I don't see ADO as two-tier because the ADO can easily be passed through multiple components, unlike a View or SQL Pass Through. I see ADO as a way to pass the data.