Support for Access V2.0
-----------------------

CASIF/Win is written in Visual Basic V3.0. This version of Visual Basic
uses the Microsoft Jet database engine V1.1, which is also the core of
Microsoft Access V1.1. This database engine is contained in file
MSAJT110.DLL, which is normally found in your WINDOWS/SYSTEM directory.
MSAJT110.DLL is distributed with Visual Basic 3.0 programs and with
Microsoft Access V1.1.

Microsoft changed the Access database format for Version 2.0 so that it
is no longer compatible with the V1.1 database engine. To accomodate
Visual Basic V3.0 programs, Microsoft developed and distributed a
"compatibility layer" library, which converts Visual Basic V3.0 library
calls to work with the Jet database engine V2.0.  This compatibility
library is contained in file MSAJT112.DLL.

However, the Visual Basic V3.0 database library VBDB300.DLL must be
changed to call MSAJT112.DLL instead of MSAJT110.DLL.  Since this
involves changing a single "0" character to a "2" in the file, there is
no need to redistribute the entire 90 Kbyte file.  The following Debug
script will make the change:

	C:\WINDOWS\SYSTEM>DEBUG VBDB300.DLL

	-E 324 <enter>
	xxxx:0324  30. 32 <enter>
	<enter>
	-W <enter>
	Writing xxxxx bytes

	C:\WINDOWS\SYSTEM>


This uses the DOS utility DEBUG. Any other binary file editor can be
used instead (e.g. Norton Utilities). Make a backup of copy of the file
VBDB300.DLL first if you aren't sure what you're doing.

The V2.0 database engine itself, file MSAJT200.DLL, is disbtributed with
Access 2.0.  The V1.1 database engine also required another library
called MSAES110.DLL - this file is no longer required with V2.0.

If you use databases other than Microsoft Access, you may also want to
change the [Installable ISAMs] section of your CASIFW.INI file to refer
to any V2.0 DLLs you have for other databases, e.g. XBS200.DLL instead
of XBS110.DLL.

