-----------------------------------------

Data Access Objects (DAO) SDK README File

December 1996
-----------------------------------------

(C) Copyright Microsoft Corporation, 1995, 1996

This file contains complementary and late-breaking

information about the Microsoft Data Access Objects
SDK (DAOSDK) Version 3.5.

If you have not yet installed the DAOSDK, you can run
SETUP.EXE directly from the \DAOSDK\Disk1 directory.

New 3.5 Features

------------------
Some features of DAO were not exposed in the DAOSDK in
version 3.0. In 3.5, all public properties and methods
of DAO are present in the DAOSDK classes. This includes
the Jet Replication features and ODBCDirect.

Notes on GetRowsEx
------------------
In 3.0, binding to Variant strings using the dbBindVARIANT
constant always returned ANSI strings, never Unicode. This
has been changed in 3.5 so that it will now return Unicode
strings in Unicode versions of the ddao35 dlls.

Building DAOSDK with older versions of VC

------------------
DAOSDK 3.5 will only support MFC versions 4.2 and higher.
This is to keep conflicts from arising between DAOSDK
libraries built with MFC41.DLL and DAO libraries built with
MFC42.DLL. Attempting to build new DAOSDK libraries with
older versions on MFC will result in a compile error. Additionally,
if you need to build DAO SDK with VC 4.2, you need to make sure
to point to the right headers. Specifically, you'll find
DBDAOINT.H, DBDAOID.H, DBDAOERR.H, and DAOGETRW.H in msdev\include.
You'll likely want to change dbdao.h in devstudio\daosdk\include to
point to the correct headers by explicitly defining the directories
where they exist.

Installing DAO SDK to a network share

------------------
There is a known bug in DAO SDK setup that you cannot install to
a directory using an UNC path (ie. \\myserver\myshare). Instead,
you need to map the share to a drive letter and install to the drive
letter. If you try to use a UNC path, your include and library
search directories will become corrupted.