Hello Stefan. Thanks for the preview. It looks like your work is several layers above mine, so there may be room to slip my lib under yours. Whether or not it will help much, it's difficult to judge by looking the the interface you posted. My first object-relational mapper used Rogue Wave DBTools++. It did help a lot but it was a run-time system and my mapper was of that kind too (that was in 1997 anyway, a long time before it was "discovered" all that you could do with templates). So currently you do all the binding to the db yourself ? Which one do you use ? What kind of mapping do you plan to support ? Vertical, filtered, horizontal, or let the user decide ? Does your tool create the tables (typical for object-relational mappers) or does it "objectify" an existing database (what I call "relational-object mapping") ? One of the many problems with ORM in presence of transactions is that you (probably) have a table that maps between persistent objects and object ids. If new objects are persisted in a transaction and the transaction is rolled back, the map must be rolled back too... J-L