couldn't find installable ISAM

[Fabri]

Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.
The software works well when run from the Visual studio ide ("run with
full compile"), so it does what I want, connecting to the database etc.
But the problem is that when I run the compiled exe I get the error:
"Couln't find installable ISAM".

I' ve checked other sites, tried to upgrade MDAC to 2.8 and also Jet to
4 but without resolutions to my problem.
Why when I run the source from visual studio it works and doesn't when
compiled?
Any help would be appreciated.
Thnx
Bye

[Ken Halter]

Post by Fabri
Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.

Try going through a couple of these....

Searched for 'installable isam'
http://support.microsoft.com/search/default.aspx?spid=2971&query=installable+isam&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a

[Ralph]

Post by Fabri
Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.
The software works well when run from the Visual studio ide ("run with
full compile"), so it does what I want, connecting to the database etc.
"Couln't find installable ISAM".
I' ve checked other sites, tried to upgrade MDAC to 2.8 and also Jet to
4 but without resolutions to my problem.
Why when I run the source from visual studio it works and doesn't when
compiled?
Any help would be appreciated.
Thnx
Bye

Idle thoughts...

Where and for what component/method do you receive this error?
Can you isolate it to a specific control if using DataBinding?

If using DAO go to the "Prog...Files\Common Files\Microsoft Shared\DAO
folder and manually register the dao components found there. Make sure DAO
3.5 appears in the references.

Check your connection strings: Jet 4 provider; nothing too funky? ; check
your syntax - quotes or double double-quotes can occasionally be an issue;
the path? (a relative path may be different in the IDE compared to a
compiled app.)
Q90111 ACC: "Couldn't Find Installable ISAM" Error Message
http://support.microsoft.com/support/kb/articles/q90/1/11.asp

Generally the error is a bit bogus unless you are specifically attempting to
connect to an ISAM database (text, excel, etc...) In which case the proper
ISAM provider/driver might be missing. If trying to connect to MSAccess it
is telling you the connection couldn't be resolved.

The fix is usually an embarrassing head-slapper. <g>

-ralph

[MikeD]

Post by Fabri
Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.
The software works well when run from the Visual studio ide ("run with
full compile"), so it does what I want, connecting to the database etc.
"Couln't find installable ISAM".
I' ve checked other sites, tried to upgrade MDAC to 2.8 and also Jet to
4 but without resolutions to my problem.
Why when I run the source from visual studio it works and doesn't when
compiled?

There are several causes of this particular error. The actual causes are not
necessarily related.

PRB: Error "Can't Find Installable ISAM" When You Connect to Access Database
with Intrinsic DataControl
http://support.microsoft.com/kb/299457/en-us

FIX: Error message "Cannot find installable ISAM" after installing localized
versions of Visual Basic 6.0 Service Pack 4 and Service Pack 5
http://support.microsoft.com/kb/273458/en-us

The following might also provide some useful information. It says it applies
to Access 2000, but it really applies to Access 2003 too since both use Jet
4.0.

How to keep a Jet 4.0 database in top working condition in Access 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300216

[Fabri]

Hi all and many thanks for your help,
I've read all the links you told me but unfortunately with no
results...aghhhhh
I've gone to the registry of my machine under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet

and I find:
3.0
3.5
4.0

I've patrched Visual Studio with the SP6 and in the references I've got
Microsoft DAO 3.6 Object Library

Visual Studio is in English and Windows Xp (Version 2002) is in Italian with
SP 2

I tried also to make a package with "Package & deployment wizard" of visual
studio, perhaps, I thought than the dll packaged could resolve the problem
but it didn't...

I tried also to make a simple project on the line of the one which doesn't
work, only one simple form with one data component.
In the "databasename" of this data component I've put the complete path to
the access2003 database mdb and the recordset type is "1-dynaset" and in the
"recordsource" I've put the name of the table of the access database to be
binded.

I'm thinking also to downgrade the Sp of visual studio to sp5 to see if can
it be a solution..

Any other ideas?

Post by MikeD

Post by Fabri
Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.
The software works well when run from the Visual studio ide ("run with
full compile"), so it does what I want, connecting to the database etc.
"Couln't find installable ISAM".
I' ve checked other sites, tried to upgrade MDAC to 2.8 and also Jet to
4 but without resolutions to my problem.
Why when I run the source from visual studio it works and doesn't when
compiled?

There are several causes of this particular error. The actual causes are not
necessarily related.
PRB: Error "Can't Find Installable ISAM" When You Connect to Access Database
with Intrinsic DataControl
http://support.microsoft.com/kb/299457/en-us
FIX: Error message "Cannot find installable ISAM" after installing localized
versions of Visual Basic 6.0 Service Pack 4 and Service Pack 5
http://support.microsoft.com/kb/273458/en-us
The following might also provide some useful information. It says it applies
to Access 2000, but it really applies to Access 2003 too since both use Jet
4.0.
How to keep a Jet 4.0 database in top working condition in Access 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300216
--
Mike
Microsoft MVP Visual Basic

[Fabri]

IT worked!!!!
Finally, what I've done:

-with the visual studio tool "Package & deplyment wizard" I've made a
package under a directory in C:
-After lauched the generated setup.exe of the package I've tried to run the
application from Start->Programs->MyApplication
but I received the same problem with ISAM.
-But If I run the application from the support directory generated by the
packaging tool all goes well!!!
It's probably because in the support dir there are all the dll that the exe
needs?

Now, I've changed the path to the application from the
Start->Programs->MyApplication to point to the exe in the support directory
and it works fine!

A question: If I have to redistribuite the application on another XP machine
do I have to install Visual Studio on that machine?

[Ralph]

Post by Fabri
IT worked!!!!
-with the visual studio tool "Package & deplyment wizard" I've made a
-After lauched the generated setup.exe of the package I've tried to run the
application from Start->Programs->MyApplication
but I received the same problem with ISAM.
-But If I run the application from the support directory generated by the
packaging tool all goes well!!!
It's probably because in the support dir there are all the dll that the exe
needs?
Now, I've changed the path to the application from the
Start->Programs->MyApplication to point to the exe in the support directory
and it works fine!
A question: If I have to redistribuite the application on another XP machine
do I have to install Visual Studio on that machine?

No.

[SQLFriend]

I am having the same problem when I run a copy of VB project from work, I
copied the whole project from work and trying to run it on my home computer,
My home computer runs WINDOWS XP sp2 and have VB6 installed. Any idea??
thanks,

Post by Fabri
Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.
The software works well when run from the Visual studio ide ("run with
full compile"), so it does what I want, connecting to the database etc.
"Couln't find installable ISAM".
I' ve checked other sites, tried to upgrade MDAC to 2.8 and also Jet to
4 but without resolutions to my problem.
Why when I run the source from visual studio it works and doesn't when
compiled?
Any help would be appreciated.
Thnx
Bye

[Ralph]

Post by SQLFriend
I am having the same problem when I run a copy of VB project from work, I
copied the whole project from work and trying to run it on my home computer,
My home computer runs WINDOWS XP sp2 and have VB6 installed. Any idea??
thanks,

Post by Fabri
Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.
The software works well when run from the Visual studio ide ("run with
full compile"), so it does what I want, connecting to the database etc.
"Couln't find installable ISAM".
I' ve checked other sites, tried to upgrade MDAC to 2.8 and also Jet to
4 but without resolutions to my problem.
Why when I run the source from visual studio it works and doesn't when
compiled?
Any help would be appreciated.
Thnx
Bye

As you will notice, there are multiple problems that can cause a "Can't Find
Installable ISAM" error. Without additional information one can only make
general guesses.

Just copying a project from one machine to another usually doesn't work
because references and components (locations and versions) often have to be
reset for the target machine. Connection Strings often have to be modified
as well.

You might open the references dialog and check to make sure there is nothing
marked as 'missing'. You might consider just re-referencing all the database
components.

The OP solved his problem by creating a package and installing it. Obviously
providing a key component which he was unable to uncover by just looking for
it. You might try the same thing - create a package at work and install it
at home.

At what point in the app does the error occur?
What is the database?
What does your connection string?
What Data Access library are you using? ADO/DAO?
Bound controls? Or unbounded?

-ralph

[SQLFriend]

1.The error occurs when I run the project, when I click on Start with full
compile from the Run menu
2. Database is SQL server 2000
3. This is my connection string:
DBConn.Open "Driver={SQL Server};server=" & txtSQLServerName & ";database="
& txtSQLDBName & ";Trusted Connection=Yes;"
4. I am using ADO 2.6 and DAO 3.6
5.. Controls are bound to excel file
.

Post by SQLFriend

Post by SQLFriend
I am having the same problem when I run a copy of VB project from work, I
copied the whole project from work and trying to run it on my home

computer,

Post by SQLFriend
My home computer runs WINDOWS XP sp2 and have VB6 installed. Any idea??
thanks,

Post by Fabri
Hello all, I've successfully compiled a source written in VB6 - Sp6
wich connects to Access 2003.
The operating system is WinXP-sp2.
The software works well when run from the Visual studio ide ("run with
full compile"), so it does what I want, connecting to the database etc.
"Couln't find installable ISAM".
I' ve checked other sites, tried to upgrade MDAC to 2.8 and also Jet to
4 but without resolutions to my problem.
Why when I run the source from visual studio it works and doesn't when
compiled?
Any help would be appreciated.
Thnx
Bye

As you will notice, there are multiple problems that can cause a "Can't Find
Installable ISAM" error. Without additional information one can only make
general guesses.
Just copying a project from one machine to another usually doesn't work
because references and components (locations and versions) often have to be
reset for the target machine. Connection Strings often have to be modified
as well.
You might open the references dialog and check to make sure there is nothing
marked as 'missing'. You might consider just re-referencing all the database
components.
The OP solved his problem by creating a package and installing it. Obviously
providing a key component which he was unable to uncover by just looking for
it. You might try the same thing - create a package at work and install it
at home.
At what point in the app does the error occur?
What is the database?
What does your connection string?
What Data Access library are you using? ADO/DAO?
Bound controls? Or unbounded?
-ralph