Last post Aug 12, 2008 02:12 AM by Mikesdotnetting
Aug 07, 2008 12:03 PM|golddog|LINK
Trying to put together a simple prototype for reading things from our sql server database and writing to an access database. I happen to be using asp.net 3.5, access 2007.
I'm getting an OleDbException with the message "Could not find an installable ISAM" when I try to connect.
I found some articles elsewhere that pointed to the registry. I see Jet 4.0 in the section under HKEY_LOCAL_MACHINES\SOFTWARE\Microsoft\Jet\4.0\Engines, so I
think it's registered o.k., but I'm not real familiar with that.
I do notice that there's no "win32" entry pointing to a dll in the Jet 4.0 folder (unlike Jet 3.x) in Engines, and there's no Jet 4.0 entry at all under ...\Jet\4.0\ISAM Formats, but I don't have enough experience with this to know whether that's indicative
of the problem.
Here's the connection string I'm using (from VS debug). I don't see any obvious typos, but maybe that's it.
"Provider=Microsoft.Jet.OLEDB.4.0;DataSource=C:\\temp\\temp.accdb;Persist Security Info=False;"
Aug 11, 2008 02:24 AM|Mikesdotnetting|LINK
To connect to an Access 2007 database, you need to use the new ACE provider:
Aug 11, 2008 10:00 AM|golddog|LINK
Thanks, Mike. Since I'd posted, I found out about that. I'd tried that after installing the provider (here if anyone else is looking:
, tried hitting a 97 sample database with the Jet connection. No dice, always the ISAM error.
Anyway, some others here are trying it out, maybe they'll see what I'm missing.
Aug 11, 2008 03:20 PM|Mikesdotnetting|LINK
A 97 database needs ODBC (ditch it!). Jet works with 2000-2003. ACE will work with 2000-2007. Oh, and as far as the source of your error is concerned (only just spotted it....) "Data Source" in the connection string is
two words - not one.
Aug 11, 2008 05:58 PM|golddog|LINK
Of course, first thing, I come in this morning and the guy who'd been looking at it said he saw, after a couple of hours, the DataSource issue as well. I'm bothered that I overlooked that, as that was
exactly the problem mentioned in many of the posts I read, but I still didn't see it.
Must've just been the end of a long week (I hope). Grrr.
Thanks again. I'll make a note to check what version(s) of Access we're expected to deal with.
Aug 12, 2008 02:12 AM|Mikesdotnetting|LINK
I'll make a note to check what version(s) of Access we're expected to deal with.
97 is no longer supported. Anything from 2000 onwards will be fine. Once you start using the Jet provider to connect from an ASP.NET app, it stops becoming and "Access" database and becomes a "Jet" database instead.