I writing an installation script with install shield 3 for a VB4.0 /
Access 2.0 / Windows 95 application, and am having trouble with getting
Visual Basic recognising not recognising DAO on the installed machine.

I have tracked it down to the following registry Keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.0\Engines\Jet 2.x]
"win32"="G:\\WINNT40\\system32\\MSRD2X32.DLL"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.0\ISAM Formats]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.0\ISAM Formats\Jet 2.x]
"Engine"="Jet 2.x"
"OneTablePerFile"=hex:00
"IndexDialog"=hex:00
"CreateDBOnExport"=hex:00
"IsamType"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\DAO]
"Path"="G:\\Program Files\\Common Files\\Microsoft
Shared\\DAO\\DAO3032.DLL"

I would have thought the 'dll self-register' option for dao3032.dll
would have installed these keys for me - apparently not.  can anyone
tell me what I am doing wrong?

These are the files I am installing for DAO:
============================================
Destination: c:\Program Files\Common Files\Microsoft Shared\Dao
Files:
------
DAO3032.dll
Dao2532.tlb

Destination: c:\WIN95\SYSTEM
Files:
MSJINT32.dll
MSJT3032.dll
MSJTER32.dll
MSRD2X32.dll
MSWNG300.dll
ODBCJI32.dll
ODBCJT32.dll
ODBCTL32.dll
VBAJET32.dll
VBAR2232.dll
VBDB32.dll
Ven2232.olb

Also, can I leave off the ODBC????.dll files (I'm not using it).  Is
there anything else I can not distribute?