Installable ISAM?

[Leo]

Other than what the error message is telling me, What is an Installable ISAM,
and why can't it be found?

Error message:
Run time error (some number)
Could not find Installable ISAM.

[huibert]

"Leo" <leod@kam-az.com> wrote:
>
>Other than what the error message is telling me, What is an Installable
ISAM,
>and why can't it be found?
>
>Error message:
>Run time error (some number)
>Could not find Installable ISAM.

This error message appears when you are trying to open an Access DB and VB
is somehow unable to open it, because your connect string is not correct.
In this case ADO/DAO mistakenly seems to think that you are trying to open
an ISAM (Indexed Sequental Access Mdon't know) file.

There is a link somewhere that describes various connect string possibilities,
but I forgot...


hth
huibert

[Sue Harsevoort]

You don't give much detail about what you are doing when you get the error,
but I had the error just the other day in a procedure in an Access database
where I was trying to DoCmd.TranasferText. The following article from the
Microsoft Knowlegde base helped me:

http://support.microsoft.com/default...;EN-US;Q171955

It is not specifically about the error message you are getting, but if your
problem was the same as mine you will see that this is also a problem.

Sue

"Leo" <leod@kam-az.com> wrote in message news:3c0f9672$1@147.208.176.211...
>
> Other than what the error message is telling me, What is an Installable
ISAM,
> and why can't it be found?
>
> Error message:
> Run time error (some number)
> Could not find Installable ISAM.

[Leo]

Thanks for the link Sue!

I was trying my hand for the first time at coding the Connection, Command
and Recordset properties instead of setting them via the control's properties
window. When I got the error, the debugger stopped at the Connection's Open
method. Is it wrong to assume that I can copy and paste the connection string
from the properties window into the code window?

This is what I've tried:

Dim myConn AS ADODB.Connection
Dim strSQL AS String
Set myConn = New ADODB.Connection
myConn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\DatabaseProjects\Kam1.mdb
Dim strDeleteWhat AS String

strDeleteWhat = txtFields(0).Text

strSQL = "DELETE From tblComputations Where JobCategoryID = '" & strDeleteWhat
& "'"

myConn.Open myConn
myConn.Execute strSQL

I'm sure there are countless errors in this example. I am using ADO 2.1
and the ADO 2.1 Programmer's Reference as my guide in diving head first into
Database programming.


"Sue Harsevoort" <SusannaH67@hotmail.com> wrote:
>You don't give much detail about what you are doing when you get the error,
>but I had the error just the other day in a procedure in an Access database
>where I was trying to DoCmd.TranasferText. The following article from the
>Microsoft Knowlegde base helped me:
>
>http://support.microsoft.com/default...;EN-US;Q171955
>
>It is not specifically about the error message you are getting, but if your
>problem was the same as mine you will see that this is also a problem.
>
>Sue
>
>"Leo" <leod@kam-az.com> wrote in message news:3c0f9672$1@147.208.176.211...
>>
>> Other than what the error message is telling me, What is an Installable
>ISAM,
>> and why can't it be found?
>>
>> Error message:
>> Run time error (some number)
>> Could not find Installable ISAM.
>
>

[David]

It all looks right to me except ending quotes around your connectin string...
Also in your criteria for the SQL statement, If JobCategoryID is a number
field then you don't need quotes around the variable...
another suggestion is to download and run MDAC 2.6 form Microsoft to update
you ADO library to 2.6


"Leo" <leod@kam-az.com> wrote:
>
>Thanks for the link Sue!
>
>I was trying my hand for the first time at coding the Connection, Command
>and Recordset properties instead of setting them via the control's properties
>window. When I got the error, the debugger stopped at the Connection's
Open
>method. Is it wrong to assume that I can copy and paste the connection
string
>from the properties window into the code window?
>
>This is what I've tried:
>
>Dim myConn AS ADODB.Connection
>Dim strSQL AS String
>Set myConn = New ADODB.Connection
>myConn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\DatabaseProjects\Kam1.mdb
>Dim strDeleteWhat AS String
>
>strDeleteWhat = txtFields(0).Text
>
>strSQL = "DELETE From tblComputations Where JobCategoryID = '" & strDeleteWhat
>& "'"
>
>myConn.Open myConn
>myConn.Execute strSQL
>
>I'm sure there are countless errors in this example. I am using ADO 2.1
>and the ADO 2.1 Programmer's Reference as my guide in diving head first
into
>Database programming.
>
>
>"Sue Harsevoort" <SusannaH67@hotmail.com> wrote:
>>You don't give much detail about what you are doing when you get the error,
>>but I had the error just the other day in a procedure in an Access database
>>where I was trying to DoCmd.TranasferText. The following article from
the
>>Microsoft Knowlegde base helped me:
>>
>>http://support.microsoft.com/default...;EN-US;Q171955
>>
>>It is not specifically about the error message you are getting, but if
your
>>problem was the same as mine you will see that this is also a problem.
>>
>>Sue
>>
>>"Leo" <leod@kam-az.com> wrote in message news:3c0f9672$1@147.208.176.211...
>>>
>>> Other than what the error message is telling me, What is an Installable
>>ISAM,
>>> and why can't it be found?
>>>
>>> Error message:
>>> Run time error (some number)
>>> Could not find Installable ISAM.
>>
>>
>