Weird Intermitent Bug/Problem With VB Accessing MS Access

[Robertb]

I'm driving myself crazy trying to figure this one out. So much so
that I think I'm within walking distance now!

The program is written and compiled in Visual Basic 6 with SP5. The
OS is Windows XP Professional.

The other day, it worked just fne. Today it doesn't. I had this same
problem a few weeks ago, but it mysteriously went away. Well, now
it's back. What did I change? I have no idea. Lot's of stuff, I
suppose. I don't access the offending program everyday, so it could
have been broken at any point.

This problem is NOT limited to just this program, but any program
using simillar data access code (see below for function).

I'm getting the following error when trying to run it: The dialog box
is displayed instead of program start:
=============================================

Run-time error '-2147024769(800700f)'.

Method '~' of object '~' failed

=============================================
Within VB, when running the program from <F5>, I get this:
=============================================

Run-time error '-2147024769(800700f)':

Method 'Open' of object' _Connection' failed

=============================================
Debugging the program brings us to this function. The offending line
is indicated:
=============================================

Public Function Phone_GetData()

Dim dbLoc
Dim db As Connection
Dim adoRecordSet As ADODB.Recordset

Set db = New ADODB.Connection
dbLoc = "C:\Program Files\PhonePad\Config.mdb"
' ********************* THIS IS THE LINE THAT BREAKS IT!
db.Open "PROVIDER=Microsoft.Jet.OLEDB.4.0; Data Source=" & dbLoc &
";"
Set adoRecordSet = New ADODB.Recordset
adoRecordSet.Open "SELECT * FROM tblPhoneNumbers", _
db, adOpenDynamic, adLockOptimistic

adoRecordSet.MoveFirst
Do
oPhone.Add adoRecordSet.Fields("PhoneName"), _
adoRecordSet.Fields("PhoneNumber"), _
adoRecordSet.Fields("PhoneOther"), _
adoRecordSet.Fields("EntryDate")

adoRecordSet.MoveNext
Loop Until adoRecordSet.EOF

' Close RecordSet
Set adoRecordSet = Nothing

' Close Database
Set db = Nothing

End Function

=============================================
Disecting the offending line verifies that all is well with the
variable:
=============================================

From Immediate window:
? "PROVIDER=Microsoft.Jet.OLEDB.4.0; Data Source=" & dbLoc & ";"
PROVIDER=Microsoft.Jet.OLEDB.4.0; Data Source=C:\Program
Files\PhonePad\Config.mdb;

=============================================
The pertinent Project References are:
=============================================

OLE Automation
Microsoft ActiveX Data Obects 2.7 Library

=============================================
I was using ADO 2.6 but upgraded the first time this error reared its
ugly head. That did not fix the problem.

Of course, Microsoft's site is of NO help. I found a few references
here & there on the 'net, but nothing specific to this problem, nor a
cure.

Any ideas??

[QuickHare]

>db.Open "PROVIDER=Microsoft.Jet.OLEDB.4.0; Data Source=" & dbLoc & ";"

Run-time error '-2147024769(800700f)':

Method 'Open' of object' _Connection' failed
A quick search of the web comes up with the following link:
http://www.utteraccess.com/forums/ac...ess602167.html
This basically suggests re-install Access, and might be linked to Access 2003
Pro. However, the forum has not been posted to for about a week, so this is as
much information as I could find.

From another newsgroup, Mike Chaple gave the following advice:

Well I have experienced those problems. Try the following:

Open you VB application, Click on Project, References, uncheck the object
that you feel could be the problem, click OK, save your project. Click on
Project, References one more time and check back the one that you
previously uncheck, Browse to the DLL (Object) to find it with the right
Path. Save and Make your project.

Hope it help

Regards

Mike Chaple

The reply was found in microsoft.public.vb.winapi under the subject line of
"Runtime error 'automation error'".

I was using ADO 2.6 but upgraded the first time this error reared its
ugly head. That did not fix the problem.

Of course, Microsoft's site is of NO help. I found a few references
here & there on the 'net, but nothing specific to this problem, nor a
cure.

Microsoft was my first port of call, and I couldn't find anything either. Google
is better as you get the complete scenario and even a working solution (mostly).

Hope this helps.
--
QuickHare
QuickHare @ Hotmail. com