run-time error '-2147467259 (80004005)': could not find file

[CrystalJim]

Win2003, XP Pro, Access 2003

Creating an Access app for a client. Installed a prototype of 1st module on
client's machine about two to three weeks ago. Every thing is fine.

Was adding some additional functionality today and when I try to open the
database I get the error that says it cannot find the file. Nothing has
changed, same path, same file name. Happens on new code as well as old code.
New code is a copy of old code!

Here is the code:

cnObject.Open "provider = microsoft.jet.oledb.4.0; " & _
"data source =
J:\Clients\Pang\DevDatabase\CertificationTraining.mdb; "

This worked a few weeks ago! Let me repeat, nothing has changed on my box.
It is not shared with anyone. Well almost nothing, my company has the auto
updates turned on, have no way to stop them.

Any ideas would be sooooo appreciated.

Thanks a bunch for taking the time to read my post and thinking about my
dilemma.


Jim

 

[Robert Morley]

First, verify manually that J:\Clients...etc., is actually valid. Maybe you
lost the network connection at some point? You can also try copying the
file to something local and changing the path just to test it out.

The second thing to try is to decompile your code (launch Access with the
/decompile switch; Google it or ask if you need more specifics on that).

Final thing (that I can think of off-hand, anyway) is to just double-check
that the Jet OLEDB provider is properly installed. It's REALLY unlikely
that it's been uninstalled, but with computers being what they are, just
about anything's possible!



Rob

 

[CrystalJim]

Robert,

Thanks for the tips. Turns out your first one was on the mark. In order to
circumvent Outlook’s security and blocking emailing the database to the
client, it’s only ½ MB, I changed the extension to mbd. Next time I will
change it to something more noticable.

Iit was your third tip, checking the Jet OLEDB provider that clued me in
though. I created a udl file and when I went to add the database...no
database! Clicked to show all files and there it was, felt like an idiot.

Well I learned a lot, thanks again.


Jim

 

[Robert Morley]

Hehehe...been there, done that! I was actually thinking that the
connection may simply have been dropped, not that the file might've been
renamed, but yeah, that'd be a problem too, wouldn't it?!?



Rob