Couldn't find installable ISAM

dapalazolo · Joined: 06 Dec 2007 Posts: 2

I have a VB6 program accessing an Access 2000 database via the Data control.
Connect is set to "Access 2000" and Default Type is "2-UseJet".

This program works fine on one of my XP SP2 computers but does not work
properly on a new PC with XP SP2 and a new install of Microsoft Office.

When running the program from Design mode it fails and I get the error
"Couldn't find installable ISAM." However, if I compile the program and run
the resultant .exe it works fine.

I have seen 2 or 3 Microsoft KB documents and have reviewed several comments
on the web about this error and I have checked all kinds of .dlls and I
believe I have all of the correct versions, etc.

Thanks.

Archived from group: microsoft>public>vb>directx

Ralph · Joined: 04 Oct 2007 Posts: 4148

"dapalazolo" wrote in message@microsoft.com...
> I have a VB6 program accessing an Access 2000 database via the Data
control.
> Connect is set to "Access 2000" and Default Type is "2-UseJet".
>
> This program works fine on one of my XP SP2 computers but does not work
> properly on a new PC with XP SP2 and a new install of Microsoft Office.
>
> When running the program from Design mode it fails and I get the error
> "Couldn't find installable ISAM." However, if I compile the program and
run
> the resultant .exe it works fine.
>
> I have seen 2 or 3 Microsoft KB documents and have reviewed several
comments
> on the web about this error and I have checked all kinds of .dlls and I
> believe I have all of the correct versions, etc.
>

If you have checked out all the docs and checked versions, then the next
step is to check your 'connection string'.

http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnaraccessdev/html/ODC_MicrosoftOfficeDeveloperForumConnectionStringParametersinMicrosoftAccess.asp

It wouldn't hurt to compare .vbp files on the machine that works with the
one on the machine that doesn't. Just because components are present on the
box, doesn't mean that is what the IDE is using.

-ralph

dapalazolo · Joined: 06 Dec 2007 Posts: 2

Thanks. I'm not using a connection string like I would if I was using ADO.
This is just the Data control. You really helped though with your last
sentence. After I installed VB on the new machine I remember inserting SP5
but I guess something happened and the SP5 install really didn't work
properly. I compared the VB files in the VB98 folder on the two machines and
some of the file versions were different. Checking Help > About on the new
machine showed that it did not have SP5 so I reinstalled SP5 and the ISAM
problem in the IDE went away.

"Ralph" wrote:

>
> "dapalazolo" wrote in message
> @microsoft.com...
> > I have a VB6 program accessing an Access 2000 database via the Data
> control.
> > Connect is set to "Access 2000" and Default Type is "2-UseJet".
> >
> > This program works fine on one of my XP SP2 computers but does not work
> > properly on a new PC with XP SP2 and a new install of Microsoft Office.
> >
> > When running the program from Design mode it fails and I get the error
> > "Couldn't find installable ISAM." However, if I compile the program and
> run
> > the resultant .exe it works fine.
> >
> > I have seen 2 or 3 Microsoft KB documents and have reviewed several
> comments
> > on the web about this error and I have checked all kinds of .dlls and I
> > believe I have all of the correct versions, etc.
> >
>
> If you have checked out all the docs and checked versions, then the next
> step is to check your 'connection string'.
>
> http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnaraccessdev/html/ODC_MicrosoftOfficeDeveloperForumConnectionStringParametersinMicrosoftAccess.asp
>
> It wouldn't hurt to compare .vbp files on the machine that works with the
> one on the machine that doesn't. Just because components are present on the
> box, doesn't mean that is what the IDE is using.
>
> -ralph
>
>
>

Ralph · Joined: 04 Oct 2007 Posts: 4148

"dapalazolo" wrote in message@microsoft.com...
> Thanks. I'm not using a connection string like I would if I was using
ADO.
> This is just the Data control. You really helped though with your last
> sentence. After I installed VB on the new machine I remember inserting
SP5
> but I guess something happened and the SP5 install really didn't work
> properly. I compared the VB files in the VB98 folder on the two machines
and
> some of the file versions were different. Checking Help > About on the
new
> machine showed that it did not have SP5 so I reinstalled SP5 and the ISAM
> problem in the IDE went away.
>

Glad it helped.

Just to be picky, DAO does use a "Connection String" of sorts, but it is
dependent on the Connection type, is built in pieces, and tends to be buried
among multiple hiding places, or worse just 'assumed'.

For all the slings and arrows railed against it, DAO is amazingly robust.

-ralph

Rima · Joined: 23 Jan 2008 Posts: 3

Hi ralph I would like to thank u so so ooooooooooooooooooooooooooooo much coz
i have been having this problem for more than one month and i have surfed
most pages on the internet to solve it but i couldn't till today when i read
ur problem and pay attention to the service pack and i have updated my pack
and it worked finallly THaaaaaaank u

"Ralph" wrote:

>
> "dapalazolo" wrote in message
> @microsoft.com...
> > Thanks. I'm not using a connection string like I would if I was using
> ADO.
> > This is just the Data control. You really helped though with your last
> > sentence. After I installed VB on the new machine I remember inserting
> SP5
> > but I guess something happened and the SP5 install really didn't work
> > properly. I compared the VB files in the VB98 folder on the two machines
> and
> > some of the file versions were different. Checking Help > About on the
> new
> > machine showed that it did not have SP5 so I reinstalled SP5 and the ISAM
> > problem in the IDE went away.
> >
>
>
> Glad it helped.
>
> Just to be picky, DAO does use a "Connection String" of sorts, but it is
> dependent on the Connection type, is built in pieces, and tends to be buried
> among multiple hiding places, or worse just 'assumed'.
>
> For all the slings and arrows railed against it, DAO is amazingly robust.
>
> -ralph
>
>
>