Installable ISAM Error (on user PC): Why So Difficult?

[Dennised]

OK here's another Error 3170 "Can't Find Installable ISAM" problem. I'm a VB5 newbie and am completely frustrated because my simple program will NOT run on some user PCs. I've read through many forums, NGs and FAQs to attack this problem, but most seem to address a problem environment much more complicated then my simple text based databases. Here is what I have.

My VB5 program uses the VB Data Control to access four small Text databases that I have separately created. (Indeed I can read these ABCD.txt DBs with Notepad.) In my program I connect to these databases with the Data Control Connect property set to "text;". I use bound Textboxes to see the record fields. I use very little code to manipulate the Data Control (move addnew etc). Now this program works just fine on my development PC (Windows XP Home), but, it just wont run on SOME other PCs. Using the Setup Wizzard to make the distribution file, I selected the "Text" ISAM, and also made sure to "include" the four databases themselves.

Here is my experience.

As I stated, the program runs fine on my VB5 development PC and also runs OK on a different Windows ME PC and also a different Windows XP (Home)Laptop PC. However, on at least two other PCs, another Windows(Home) and a Windows (Professional) PC, I get the dreaded Error 3170 "Can't Find Installable ISAM" problem when users try to run the program. The program installs fine on these problem PCs, but it will not run.

Must I concern myself with user registry tweaks, chasing Down DLLs and DLL dates, installiing "MDACs" (whatever these are and on which PCs to install the MDACs on) or is the solution to this "Can't Find installable ISAM" as simple as my program is?

I'm just about at the end of my rope on this and would appreciate any help at all. Thanks in advance.

Dennis

 

[CCLINT]

Try adding MDAC 2.5 to the Redist folder of your VB6 PDWizard directory.

You may need to add it to the distribution medium and if necessary have the user run it once.

 

[Dennised]

Thanks CCLINT for the advice, but I'm using VB5. I see no Redist folder or PDWizzard directory off my VB5 directory or anywhere else.

Is MDAC 2.5 applicable to VB5? Where do I get this?

I'm still spinning my wheels on this problem and getting no where fast.

Dennis

 

[CCLINT]

MDAC:

http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp

 

[CCLINT]

Read this also:

http://support.microsoft.com/default.aspx?scid=kb;en-us;184265

 

[udaisengupta]

Dennis,
I faced a similar problem and have finally solved it. Why dont you see the thread: thread222-547315. May be this can help you solve your problem if it hasnt resolved itself already.



Best Regards,
Yours sincerely,
Udai.

 

[xathras]

Hi Dennised, I had this problem yesterday, I got round this via the following methods:

Installed the new version of MDAC, reinstalled Microsoft Office, and then got the lastest service pack for Visual basic, this solved my problem.

 

[Dennised]

Thanks everyone for the pointers and suggestions.

I solved this very sticky problem by simply saving my simple text database table as file.txt from MS word instead of Excel. That's it. Problem gone.

Before I had created the same text file with Excel and saved it as file.csv. Now when the used installed my program, this file is identified in Windows XP as an "Excel" csv file. I believe that was causing the user PC to look for an Excel ISAM that wasn't there. Anyway, keeping the file as pure file.txt has eliminated the problem all together. No more "Can't find installable IASM" messages and the program runs fine.

Dennis