The hard part in evaluating these technologies is finding independent research. Each OODBMS vendor will skew things to their benefit. The reason I pointed you to Ted's blog is because he's well known in both the Java and .Net camps and has attempted to write his own O/R Mapper more than once. He knows his stuff and knows it well.

>Thank you for your suggestions.
>IMHO Cache' is not object-oriented DBMS. Their "post-relational" concept is more attractive from just storing objects in database or maitaining object layer on top of RDBMS.
>
>We will continue investigating and check our test projects. I understand that EVERY new language is usually sick in IDE, error handling, etc. (First tool for HTML was also text editor even without syntax highlight). But while this could be fixed in future it is not an issue. And Cache' tools are developing.
>
>At the moment we do not plan to use Cache' ObjectScript for extensive programming. We just want to define, store and query our data in more natural way corresponding to complex logical structure of our data domain. Most of our data analysis code (and client GUI) will be still VFP and .NET applications and servers.