Acropolis seems to be more of a connector framework... you have an ORM or DAL for your data access (like SF) and then you use Acropolis to create modules for your application that can be hotswapped.  So, essencially, Acropolis is really just the next evolution of the Enteprise Library or CAB (Component Application Blocks) from MS.  Looking at the documentation, I don't see anything within Acropolis that says it provides the data access.  They're relying on either ADO.NET, LINQ to SQL to provide the data access or another DAL like SF for the data access.  STrataFrame helps you to organize your application and tie in your business logic.  You will be able to use it with any UI system, whether that's an Acropolis module, WPF, Win or WebForms.

Just like any other Microsoft framework product, there are many good ideas and tools that come from it.  StrataFrame always capitalizes on these released products when we see that it will add long-term benefits to our developers.  For example, LINQ and WPF will both be big parts of the next major release of StrataFrame as this is the direction the industry is going and both of these technologies will add great benefit to our developers.  But we mostly concerned about helping our developers create real world applications and how scalable, efficient, fast, and ease of maintanance these development environments are.  So if we see merit in these tools, without hindering performance, then we will definitely try to take advantage of them.

I know its very early to be asking this but I just wanted to get an idea of how you guys foresee this playing out.  With MS's announcement of the Acropolis framework I am very interested to know how StrataFrame will be incorporated (if at all) into this new framework.  Can we expect some kind of merger between the two or will we have to make a choice?