Re: Error Message: Can't find Installable ISAM


"stuart" <stuart.medlin@xxxxxxxxxx> wrote in message
news:af2921d4-cea6-494a-9bb0-a81388575cf4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ralph,

I appreciate the help you have given me so far in trying to fix this
problem. Here is what I have found out, based on your suggestions:

1. The database is residing on my machine, currently in c:\ (for
simplicity sake)

2. I have Jet 4.0 service pack. I checked the Msjet40.dll version
and I have version 4.0.9511 (Windows XP, SP3)

3. I created a new project, added the MS DAO 3.6 reference, copied
the code to the button click event and tried it out. This does
work.

4. Next, I added the Data control to the form and tested the
following scenarios:

a. Connect property set = Access;
Default type = Use Jet

Error Message = "Couldn't find Installable ISAM"

b. Connect property set = Access (without the
semicolon)
Default type = Use Jet

Error Message = "Unrecognized database format"

c. Connect property set = Access
Default type = ODBC connection

Error Message = "Data source name not found and no default
driver specified. "

d. Connect property set = AccessTest
Default type = ODBC connection

Error Message = "Invalid Argument"

(On this test, I used "AccessTest" for the Connect property.
This is the name I set up under the User DSN. I also tried testing
using AccessTest2 under
the System DSN and got the same error message).

The database is Access 2000 database, which I then tried converting to
Access 2002/2003 format and tried this as a possibility, but no
difference in results. One question I do have is when I created the
User and System DSN's under the ODBC data sources, should those
options show up as a selection under the "Connect" property of the
data control?

Thanks for your help!


For the last question my guess is yes, both should be offered as options.
But haven't tested it and my memory is faulty.

Ok, you did your upgrade and/or tested it. Everything checked out? You
pasted the code I gave you into a fresh standard app. (Forget the Data
Control for now) And it did not work? Correct? That's bizzare. I'm stymied.

You do worry me a bit with playing with converting formats. MSAccess does
provide a new ACEDB format. This format is NOT compatible with DAO or ADO
which is currently limited to the Jet 4.0 format. So keep it a MSAccess 2000
compatible database.

Have you tried to create a test database and connect to it, using the code I
gave you?
Again forget about playing around with other controls. If the code I gave
you doesn't work, then nothing else is going to work. There is something
else going on.

When you created your test mdb. Did you place it in the same folder as your
testApplication?

I'm just flaying here. <ha>

If I think of anything else I report back.



.