>We are not currently using the ADO.Entity framework. I guess common depends on what space your working in. We are in the enterprise space where DB2 is fairly common. In this case DB2 doesnt seem to be fully supported. We would need to keep track of data access classes across versions and it would not be supported in the BO tools or would require additional effort. That’s not necessarily a show stopper but its something that the project manager needs to be aware of.

The DB2 for non entity framework access is not a big deal since there was one that worked before. The nice thing about frameworks such as mm is you get the code class which is based after the framework data access and can tweak it if needed to suit your needs. If OakLeaf doesn't get asked for DB2 data access classes, they may not spend the time to update them or re-test them. I would ask and see where they are with them.