L
Lee Ottaway
I'm working on a project where I'm gradually phasing out an Access
2000 application with one written in VB.NET 2003 using the same
database as a back end. The company wants to phase out Access
altogether in favor of SQL Server within about a year. I can't just
drop Access altogether because the users still have to enter most of
their data through it's front end, but neither do I want to code
everything in my .NET application using OLEDBConnection since they'll
be a lot of work to convert it all over to SQLConnection in a years'
time.
It occurs to me that the best solution would be to use SqlConnection
but connect to the Access database. Can this be done in any way? Is
there a better solution that I'm missing?
Lee
2000 application with one written in VB.NET 2003 using the same
database as a back end. The company wants to phase out Access
altogether in favor of SQL Server within about a year. I can't just
drop Access altogether because the users still have to enter most of
their data through it's front end, but neither do I want to code
everything in my .NET application using OLEDBConnection since they'll
be a lot of work to convert it all over to SQLConnection in a years'
time.
It occurs to me that the best solution would be to use SqlConnection
but connect to the Access database. Can this be done in any way? Is
there a better solution that I'm missing?
Lee