Update: Early Adoper has also picked up on the significance of using SQL Server Express (SSX) to replace Jet. Go there and read the example code. Kent Tengles shares some caveats to remember accessing SSX from OLEDB. Via Benjamin Mitchell.
Ok, a little hyperbole. Access will probably never die. However, the Jet engine can be replaced!
In his post about changes to ASP.NET 2.0, Shanku Niyogi, announces that AccessDataSource, which enabled binding to Access databases using the Jet engine is being dropped in favor of one that provides binding to SQL Server 2005 Express Edition. Some are upset, believing that Microsoft is pushing people toward SQL Server Express Edition as a marketing ploy. However, Benjamin Mitchell, and the rest of us that have had to deal with Access databases that have long outgrown their britches are rejoicing.
As referencd in the SQL Server 2005 Express Edition Overview, The key enabling feature on SQL Server Express Edition is XCopy deployment of database files. Now you can deploy real, robust databases as easily as you could the very corrupatble access database files.
MSDE was a notorious deployment bad boy. The Express Edition Overview, referenced above, explains that the problematic merge module technology is no longer available. However that presents a non-trivial deployment story. A self-installing executable or MSI file can be used. There is also a 36M auto-installing web download available. Either way, a seamless installation is probably not easily doable. The Jet installations are 4 MB although there is a different one for each operating system. More over SQL Server 2005 Express Edition requires that the .NET 2.0 runtime also be installed. Some installation creativity required.
The Express Edition install includes 50 product licenses, meaning that up to fifty programs can use the Express Edition engine for free. You only need to install it once. If only it were part of the operating system... Looks like we may have to wait until 2008 for that.