The first paragraph of this page is as follows:
"The Jet database engine is provided by Microsoft® Internet
Information Services (IIS) for Microsoft Access databases. This
database engine is a popular alternative to Microsoft SQL Server and
is useful for low-volume Web applications. The Jet database engine is
OLEDB-compliant and is supported by classes in the Microsoft .NET
Framework System.Data.OleDb namespace"
Right off the bat, it assumes the developer's goal is to create web
applications. What if all you want to do is bring an existing stand
alone Access app into the dotnet world? I have been digging for some
time now, looking for specific info on how to bring an EXISTING,
widely distributed Access 2000 or 2003 application into the dotnet
world. As far as I can tell, Microsoft is slowly giving up on Access
and VBA as a serious development platform. I seriously hope I am
wrong about this. Can someone explain?