Will Microsoft ORM products ever support the ubiquitous MS Access?
I want to create a Domain Specific Language for a product that specifies a published MS Access Schema as it’s generalized medium for all ETL processing between external systems and the product suits flagship product (a document management system). To do this I need to be able to express concepts through the DSL that will perform CRUD operations over this ETL schema and therefore MS Access Databases. I also want to employ an ORM to achieve the data access yet sadly to do this I am still stuck with plain old ADO.Net considering that LINQ TO SQL and the Entity Framework don’t support Access and I have experienced the pain of trying to achieve this with ActiveRecord so I am left asking myself this question:
“Will Microsoft or anyone else for that matter, provide us with an ORM product that works nicely with Microsoft Access and doesn’t hit my wallet”
I am not a big Access fan per se, in fact if you ask those that know me well they would probably get a good laugh out of the fact that I am working with it, however it surely hasn’t escaped the mass of business’ developers who have to deal with it on a daily basis, that they have to this point been ignored with regards to support from the new ORM products. Let’s hope that someone helps us out with an Entity Framework provider soon, LINQ To SQL I am pretty sure would be a complete no go zone in light of recent announcements.
2 comments








