Files Included in Jet 2.0/ VB 3.0 Compatibility LayerLast reviewed: July 20, 1995Article ID: Q113685 |
The information in this article applies to:
- Microsoft Visual Basic programming system for Windows, version 3.0
SUMMARYThis article lists all the files that come with the Microsoft Access 2.0/ Visual Basic 3.0 Compatibility Layer (also known as the Microsoft Jet 2.0/Visual Basic 3.0 Compatibility Layer). See the "Background Information" section at the end of this article for more information about the Compatibility Layer.
MORE INFORMATIONFiles Included with the Compatibility Layer The Compatibility Layer consists of the following files:
FileName Size in bytes Date Description
SETUP.EXE 39856 3/24/94 Application that installs the compatibility layer. ACC2COMP.TXT 19513 3/24/94 The readme file. MSAJT112.DLL 17424 3/24/94 The Microsoft Access 2.0 compatibility layer. VBDB300.DLL 95200 3/24/94 Microsoft Visual Basic to Access support DLL. BTRV200.DLL 110592 3/24/94 Btrieve ISAM driver library. PDX200.DLL 231888 3/24/94 Paradox ISAM driver library. XBS200.DLL 295712 3/24/94 Microsoft FoxPro ISAM driver library. CRWACC20.EXE 13376 3/24/94 Program that modifies Crystal reports files to work with Access 2.0 databases. PDBJET.DLL 96784 3/24/94 Crystal Reports file. PDCTJET.DLL 68112 3/24/94 Crystal Reports file. PDIRJET.DLL 71184 3/24/94 Crystal Reports file. Background InformationVisual Basic version 3.0, released in May of 1993, includes support for the Microsoft Access version 1.1 database engine. This provides Visual Basic developers the ability to create and distribute royalty-free applications with Microsoft Access as the underlying database. Microsoft Access version 2.0 contains a new file format that Visual Basic version 3.0 cannot access. To provide this capability, Microsoft created the Microsoft Access 2.0/Visual Basic 3.0 Compatibility Layer. To install and use the Compatibility Layer, you must have installed both Microsoft Access version 2.0 and Visual Basic version 3.0. Then the Compatibility Layer bridges the gap. Use of the Compatibility Layer is optional. Microsoft Access version 2.0 reads and writes Microsoft Access version 1.1 databases, so Visual Basic- based applications that use Microsoft Access version 1.1 databases do not need to be converted even if users upgrade to Microsoft Access version 2.0. The setup file does not remove the Microsoft Access version 1.1 files, but Visual Basic will be using the Microsoft Access version 2.0 files, once setup is run and the appropriate .INI files are edited to point to the new IISAM driver libraries. Visual Basic-based applications that use Microsoft Access version 1.1 format databases will continue to operate because Microsoft Access version 2.0 reads and writes Microsoft Access version 1.1 format databases. Visual Basic-based applications that create Microsoft Access version 1.1 format databases can continue to do so through the Microsoft Access version 2.0 files simply by changing a setting. This is documented in the ACC2COMP.TXT file that comes with the Compatibility Layer.
|
Additional reference words: 3.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |