Re: Accessing mdb file via VB code

Tech-Archive recommends: Fix windows errors by optimizing your registry


"AK" <nospam@xxxxxxxxxxx> wrote in message
news:%23T1ULFvnGHA.4648@xxxxxxxxxxxxxxxxxxxxxxx
Thanks guys, your info was good and I was able to get one of my forms up
and
running, but then I encountered the error message "Unable to find
installable ISAM" when a connection to my database was attempted on
another
form.( Man , talk about learing to ride your bike while trying to dodge
bricks!)

Googled this and went to MS KB where it talks about such a message but the
info they give (at KB # 283881) appears to deal with Access 2003 (which is
what I am using) but then goes on in the body to indicate that I am
supposed to look for a JET 3 file ! My provider is Jet 4.0 not Jet 3.


I am not afraid to edit the registry (Well I kinda sorta am but still can
do it if need be) but I am unclear if this KB article applies to me. All
of
my connections are to the same DB and the conection string is the same:

Private m_adoConnection As ADODB.Connection

Dim strConn As String

strConn = "Provider=Microsoft.Jet.OLEDB.4.0;Data " & _
"Source=" & m_sDataFile & ";" & _ 'm_sDatafile is my
path
to my Database
"Jet OLEDB:Database Password = MyPassword; &
Mode=ReadWrite;"

m_adoConnection.Open strConn

What gives now??

Any

<snipped>


If the situation in the KB article is not related to your problem (you are
not using an ISAM driver) then you have the "bogus" form of that error.
There are several causes and respective solutions that will vary from the
simple to a drift toward madness.

Are you using the ADO or DAO data access libraries?

If you are using ADO and ADO providers are you by any chance using a "DAO"
control (DataGrid) on this second form?
If so you will need to make sure the DAO components and typelib are
installed and registered. You should find them in Progr~Files\Common
Files\Microsoft Shared\DAO. This is the simple fix.
[Occasionally these files are not correctly installed or registered on WinXP
boxes with Jet4. Also be aware - the problem is not that you are using or
accessing DAO from your program, the problem is that these controls need the
DAO to be properly installed. Therefore this has nothing to do with project
references.]

If that doesn't solve the problem then try this...
http://support.microsoft.com/default.aspx?scid=kb;en-us;299457
Make sure you have only one MSVBVM60.dll on your machine.

If that doesn't seem to resolve the problem, then it is caused by another
miss-match of components. If you are still having trouble report back with
all the specifics of your problem domain. (Data Access Libraries, OS
version, Jet, MDAC, etc.) You can fiddle away one by one, or simply burn
everything MDAC/Jet down to the water line and start over.

hth
-ralph


.

Relevant Pages

  • Re: Getting the value of a dynamically modified Jet registry values
    ... ADO retains the values you set, ... If you use DAO, you have to remember what values ... > registry, reading the registry does not help. ... > applies to all session defined parameters. ...
    (microsoft.public.access.modulesdaovba)
  • Re: How to enforce subtypes/supertypes in Access 2000?
    ... DAO is the native object model for Jet databases and, as such, is the ... ever need ADO. ... Private Sub SetContactType() ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Access 2007 and VB
    ... and link to the download as a non expert some ... There is a bit of confusion with ADO access to the new MSAccess ACCDB ... You could reference "DAO". ...
    (microsoft.public.vb.general.discussion)
  • Re: Access 2007 and VB
    ... "unrecognized database format" ... There is a bit of confusion with ADO access to the new MSAccess ACCDB ... You could reference "DAO". ...
    (microsoft.public.vb.general.discussion)
  • Re: Access 2007 and VB
    ... "unrecognized database format" ... There is a bit of confusion with ADO access to the new MSAccess ACCDB ... You could reference "DAO". ...
    (microsoft.public.vb.general.discussion)