The three DLLs that were comprised by Jet 2.0 were the Jet DLL, the Data Access Objects (DAO) DLL and several external ISAM DLLs. DLLs in Windows are "libraries" of common code that can be used by more than one application-by keeping code that more than one application uses under a common library which each of these applications can use independently code maintenance is reduced and the functionality of applications increases, with less development effort. Jet 2.0 was released as several dynamic linked libraries (DLLs) that were utilised by application software, such as Microsoft's Access database. A retrofit was provided that allowed Visual Basic 3.0 users to use the updated Jet issued in Access 2.0. Jet became more componentised when Access 2.0 was released because the Access ODBC developers used parts of the Jet code to produce the ODBC driver. That's why they've had all those Jet/ODBC problems in VB 3.0." For VB 3.0 they basically had to tear it out of Access and graft it onto VB. "It would be reasonably accurate to say that up until that stage Jet was more the name of the team that was assigned to work on the DB engine modules of Access rather than a component team. Tony Goodhew, who worked for Microsoft at the time, says Cirrus was developed from a pre-release version of Visual Basic code and was used as the database engine of Microsoft Access. Jet originally started in 1992 as an underlying data access technology that came from a Microsoft internal database product development project, code named Cirrus.
How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine.Release manifest for MDAC 2.5 Service Pack 3 (.2).INFO: MDAC Version 2.6 and Later Do Not Contain Jet or Desktop ODBC Drivers.Release manifest for MDAC 2.1 (2.11) (GA).Microsoft Data Access Components (MDAC) release history.INFO: Identifying the Jet Database Engine Components.
Microsoft Access 97 / Excel 97 / PowerPoint 97 / Word 97
0 kommentar(er)
