• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 19. Linking Access Front-Ends to... > In the Real World—The (Almost) Free ...

In the Real World—The (Almost) Free Lunch

Controversy over the future of conventional shared-file multiuser Jet applications continues unabated among Access developers and Microsoft marketers. The shared-file, “Jet is alive and well” axis insists that Jet is a viable back end for workgroup-size online transaction processing (OLTP) applications. The “Jet is dead” cabal, whose membership is dominated by SQL Server marketing folks, consider MSDE to be Microsoft’s “strategic database” for Office applications and SQL Server 2000 to be the natural back-end choice for everyone else, including users of hand-held devices running Windows CE. Regardless of the rhetoric, you can’t beat the price of MSDE; it’s free.

Shared-file proponents tend to favor traditional Data Access Objects (DAO), a mature technology now in its final version (3.6). Members of the MSDE/SQL Server clan justifiably promote OLE DB and ActiveX Data Objects (ADO) as being where the action is for database connectivity. OLE DB and ADO are designed to support Web-based applications; DAO isn’t. ADP use OLE DB and ADO to connect to SQL Server. Microsoft’s .NET framework is centered on SQL Server and an enhanced version of ADO called ADO.NET, and you can expect major changes to Access when Microsoft finally gets around to releasing the next version of Office. Access versus Next undoubtedly will toll the death knell for new Jet-based applications and DAO.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint