MS access 2000 and ASP.NET interoperability

[rufus]

I have started a new project that requires an existing MS Access 2000
application to be written using asp.net web forms. We have downloaded a MS
Access -> ASP.NET converter (www.microtools.us) and converted the access
forms. The code looks quite messy and I'm not sure whether it will save us
much development time.

Another requirement is that all data access and authentication functionality
is to be encapsulated in a series of classes that act as a middle tier
between the web forms and the data source. The tricky part about this is
that they also want this middle tier to sit between MS Access and the data
source. The idea behind this is that most future modifications can be done
once on this middle tier and are seamlessly reflected in both the ASP.NET
and MS Access applications.

My question is: Is this really possible? If so, can anybody give me some
advice on the architecture, platforms and technology I should be using.

Thanks in advance.

Chris

 

[Scott M.]

Not only is it possible, but it is a very normal, popular and wise approach
to take. My advice though is to re-write the application from scratch
because the conversion most definitely does not take advantage of the
powerful features of ADO.NET.

 

[rufus]

Not only is it possible, but it is a very normal, popular and wise approach
to take. My advice though is to re-write the application from scratch
because the conversion most definitely does not take advantage of the
powerful features of ADO.NET.

Thanks for your reply. Can you think of any articles I could have a look
at? How do I use the classes I have created in dotnet with my access
application?