Couldn’t find installable ISAM (VB6)

Topic

New Reply

My VB6 program retrieves and updates a mdb database. It works fine in my system (with Windows XP and MS Office 2000), It also installs and works without error in other Windows XP computers. But when installed and run in a Windows 98 computer without Microsoft Access, “Couldn’t find installable ISAM” error occurred whenver the VB6 program tried to the mdb file. Apparently some files are missing in that computer.

In my installation program, DAO 3.60 (MDAC 2.5, dao360.dll, & MSJet 4) is included in the package. I use Installshiled DevStudio MSI for the installation.

Can someone please help by pointing out or leading me to the cause(s) of this erro?

Reply | Quote

Replies

(Edited by HansV to make URL clickable – see Help 19)

With reference to Access board’s post 209793, I am using VB6 SP6 and the version of my msvbvm60.dll is 6.0.88.42 that comes with Installshield DevStudio SP1’s merge modules.

Reply | Quote

Does any of these help?

FIX: Error message “Cannot find installable ISAM” after installing localized versions of Visual Basic 6.0 Service Pack 4 and Service Pack 5
PRB: Error “Can’t Find Installable ISAM” When You Connect to Access Database with Intrinsic DataControl

Reply | Quote

Thanks for your lead, Hans. The computer with problem isn’t with me right now. I’ll get back to you after I have tested the Microsoft’s solution.

Reply | Quote

I browsed through the folders in the computer with problem and discovered that MS Access 2000 was actually installed but somehow was corrupted. Since the original Office CD wasn’t available, and Access wasn’t working anyway, I took the drastic action of deleting all occurences of DAO 360 in the registry (op! Heaven forbids). I reinstall my VB6 program and this time it worked but still not properly. There were times like error “3264 – No field defined: cannot append TableDef or Index” which never appears in aproperly installed program.

I deduced that the fault lies with the particular system. My installation program thought that DAO 360 was installed (which it wasn’t or was missing from the computer) and didn’t install the DAO 360, causing a lot problem to my program. I assumed my program would work correctly once the mess with corrupted Access 2000 was cleared with re-installation of MS Office. Is my deduction logical?

Reply | Quote

Reinstalling Office Pro is the logical next step, but this kind of problem can be hard to solve. Good luck!

Reply | Quote