------------------------------------------------------------------------------
            How to Correct "Couldn't find installable ISAM" error
------------------------------------------------------------------------------

This file expands upon the information given in the VB's help file and
its README.TXT.  This includes common errors and traps that have been
noted in messages in the MSBASIC forum on Compuserve related to this
error.

"Couldn't find installable ISAM" means that an external file dynamic
link library (DLL) file couldn't be found.  This file is required for
operations such as attaching or accessing external tables.  External
databases that are affected by the error include: Btrieve, dBase III,
dBase IV, FoxPro 2.0, FoxPro 2.5, and Paradox 3.x.  ODBC and MS-Access
databases use different methods and DLLs for connecting.

Possible causes when program doesn't work in the VB design environment
or as an EXE file:

  1)  The entry for the database type you are trying to access in the
      [Installable ISAMs] section in VB.INI or <appname>.INI points to
      an incorrect location.  For example, VB.INI for some reason has
      its entries pointing to C:\WINDOWS\SYSTEM when your Windows system
      directory is actually on G:\WIN31\SYSTEM.  To correct this problem
      exit VB or your app and edit the appropriate .INI file with Notepad
      or another ASCII editor.
 
  2)  The entry for the database type you are trying to access in the
      [Installable ISAMs] section in VB.INI or <appname>.ini points to
      a network drive, and that drive isn't connected.  Check to make
      sure the network is available and the proper drive letter is
      established, and try the operation again.
  
  3)  The entry in the [Installable ISAMs] section in VB.INI or
      <appname>.INI does not exactly match the connect property of your
      data control or the connect parameter in the OpenDatabase function.
      Confirm that the Connect property and the entry in the .INI file
      match, and try the operation again.
   
      Examples of this error:
   
      a.  The VB manuals and help file refer to the Connect property for
          a Paradox database as 'Paradox;'.  Actually, VB writes
          'Paradox 3.x;' to the VB.INI file.  
          
      b.  Here are a couple of common typos:
      
          Typo               Correct
          ----               --------
          'dBase;'           'dBase IV;' or 'dBase III;'

          'dBaseIV;'         'dBase IV;'
          
          'dBaseIII;'        'dBase III;'
          
          'FoxPro;'          'FoxPro 2.0;' or 'FoxPro 2.5;'
    

Possible causes when program works OK in the VB design environment but not
as an EXE file:

  1) You have not created an <appname>.INI file for your application
     or your current .INI file does not have an [Installable ISAMs]
     section in it.  To create the required .INI file or to add this 
     section to your current .INI, simply load your VB.INI file into
     Notepad (or another ASCII editor) and copy the [Installable ISAMs]
     section into a new file called <your_app's_name_here>.ini or
     into your current .INI if you have one.
       
  2) Your application cannot find <appname>.INI.  To correct this, use the
     SetDataAccessOption command to point to it.  For Example:
   
      SetDataAccessOption 1, app.path & "\MYAPP.INI"
     
     or
     
      SetDataAccessOption 1, WinDir$ & "\MYAPP.INI"
      
      (where WinDir$ was set to the Windows directory using the 
      GetWindowsDirectory API call)

     Using the SetDataAccessOption is the best way to prevent possible
     problems when you deliver your application to end users.   
     
------------------------------------------------------------------------------

  I hope this helps you in working with VB 3.0 and its Data Access
  functions.  I've noticed that many people have left messages in
  the MSBASIC forum describing problems with this error message.  This
  information should help you get over this hump.  If you have and
  additions or corrections to this document, let me know.
     
  You may contact me at:

  J. Frank Carr
  1532 Amber Trail
  Duluth, GA 30136  USA

      Voice Mail: (404) 880-5762 

             CIS: 75120, 2420

  America OnLine: JFCarr
 
------------------------------------------------------------------------------

