The VB program appears "COULDN't Find Installable Isam." What meanings?
Reply:
The following is for VB 3.0 and VB 4.0 16-bit versions. VB 5.0 Reference reference QA000156 "VB 5.0 Error Message COULDN't Find Installable ISAM". There are two cases of "couldn't find installable isam." This error message appears: 1. The initial test file (.ini) can not find or set incorrectly; 2. Required driver (. Dll) . VB 3.0 supported databases can be divided into five types, Microsoft Access, Btrieve, XBase, including DBase III, DBase IV, FoxBase, FoxPro for MS-DOS / Windows, Paradox, and ODBC (including Oracle, SQL Server, etc.), each The drivers and initial test files used by the class database are not the same. The drivers required for various programs can be seen below.
Database Category Driver Microsoft Accessmsaes110.dll, Masajt110.dll, VBDB300.dllbtrievebtrv110.dllxBasexbs110.dllparadoxpdx110.dllodBCODBC.DLL, ODBCINST.DLL, ODBCINST.INI, ODBCINST.HLP
In addition to Microsoft Access, database programs are not working if there is no corresponding initialization file. The database uses vb.ini and appname.ini as an initialization file: Use the vb.ini file when designing and debugging the program in the VB integration environment, while using AppName.ini after compiling into .exe files, the appName refers to. The file name of the EXE file. In addition, some of the initialization of the BTRIEVE database is set in the [Btrieve] section of the Win.ini file. The designer can change the file name or path of the default initialization file in the program, such as: SetDataAccessOption 1, "C: /VB/Data.ini". This statement must appear before all database operation statements. From your situation, the program runs normally in the VB integration environment, and cannot run after compiling .exe files, obviously the appname.ini file setting is incorrect. You can check if this file exists. If there is, you can compare this file with the vb.ini file to check if the setting is correct. The general setup file is as follows (the user's pathname may be different from this example): [ISAM] pagetimeout = 5 maxBuffersize = 128 lockretry = 20 commitLockretry = 20 readaheadpages = 16 [installable isams] paradox 3.x = c: / windows / system /pdx110.dll foxpro 2.0 = c: /windows/system/xbs110.dll foxpro 2.5 = c: /windows/system/xbs110.dll dbase III = C: /Windows/system/xbs110.dll dbase iv = C: / Windows /SYSTEM/xbs110.DLL Btrieve = C: /WINDOWS/SYSTEM/btrv110.DLL [Paradox ISAM] PageTimeout = 600 ParadoxUserName = Joe User ParadoxNetPath = P: / PDOXDB /; PARADOX.NET file path CollatingSequence = Ascii [BTrieve ISAM] Pagetimeout = 600 [dbase isam] PageTimeout = 600 century = Off Date = american mark = 47 deleted = on "couldn't find installable isam." The error can be captured in the program in the program (error number 3170) A user-friendly software should write the correct settings to the initialization file when an error occurs. The above discussion is based on VB 3.0, and if you encounter a similar error when using VB 4.0, the situation will be different. In VB 4.0, the information about the DLL file is saved in the system registration database regardless of the 16bit version, or the 32bit version (ie VB 3.0 [Installs] section) is saved in the system registration database, and the user should use the regedit of Windows 3.x or Windows 95. EXE to check if this setting is correct. This issue is replied by Li Hai.
