EntityFramework3.5\4\DataProviders

[eg]

Are there any other .net data providers for the entity framework, other
than SQL Server? I am looking for an ODBC and MS Access driver that
will work with 3.5 and 4.0 Entity Frameworks?

TIA

 

[Gregory A. Beamer]

Are there any other .net data providers for the entity framework,
other than SQL Server? I am looking for an ODBC and MS Access driver
that will work with 3.5 and 4.0 Entity Frameworks?

None at present. Not sure what the future holds.

If you want an O/R Mapper that works with other databases, however,
there are options.

In addition, if you can build the transport, the POCO option in .NET 4.0
(EF 4.0?) gives you a CLR compliant model to work with and objects that
actually "make sense". If you object is to sell a product that can use
multiple types of DBMSs, then POCO is an option, realizing you will only
get the drag and drop mapping goodness in SQL Server and will have to
populate with other languages. It is not the same as EF for everything,
but it is a way to start. You can always swap out data transports later
if EF migrates, so it is a decent path.

If you are not setting up for multiple data stores, then it could be
overkill.

Peace and Grace,

--
Gregory A. Beamer (MVP)

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************

 

[Mary Chipman [MSFT]]

As Gregory said, there is nothing like that at present, nor is it
likely in the future. If you are interested in the Entity Framework,
I'd recommend migrating the data store away from Jet/ACE(Access
2007)/ODBC to SQL Server. If you are building the kind of application
that Access is suited for, then the EF is probably overkill. If you
need the features and functionality that the EF provides, then you
need a suitable database engine. HTH,

--Mary