• OO Querying... what would it look like:

    Create Object qqMyQuery as Query;

    qqMyQuery.addtable.Table1;

    qqMyQuery.addtable.Table2;

    qqMyQuery.addtable.Table3;

    qqMyQuery.tables.addjoin(Type="Inner","Table1,Table2");

    qqMyQuery.tables.joins.addcriteria(Table1.Col1,Table2.Col2);

    And so on. Is something like that what you're looking for? Where you'd create objects based on definitions, and then would have to access methods and assign properties?

    Frankly, I don't think that works so well. If you really want to try it out, download the free trial of Cache. It's an OO DB. Instead of tables and columns, it has objects and properties. You can do things like "MyTable.Col1.value=1", instead of the T-SQL "update MyTable set Col1 = 1". Data storage is all multi-dimensional arrays. It's designed to work with .NET directly.

    If you don't like SQL, try it. Seriously.

    Personally, I've done so, and I'm sticking with SQL, for the simple reason that it's a LOT easier to build and operate a database in it. For me, anyway.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon