As I often ask, do you want to treat the the symptoms or solve the
problem? I suspect the *problem* isn't the failure to open the folder
using Network Neighborhood programmatically.

the error you quoted. This from MSDN: "AD0 2.7: Provider Errors:
When a provider error occurs, a run-time error of -2147467259 is
returned. When you receive this error, check the active Connection
object's Errors collection, which will contain one or more errors
describing what happened."

Perhaps you could follow the above instructions and post the *ADO*
error descriptions rather than the VBA run-time error.

--

"Marius" wrote in message ...
For sure it is not the problem that someone is opening
exclusively the database. The error reported in err.no -
2147467259. Once again, my solution is manually opening
the folder using Network Neighborhood (or Explorer) -
after that the connection can be opened without error.
What I need is to programatically mimic the usage of
Network Neighborhood or something similar to refresh (???)
the connection - apparently the database host computer is
not found.
-----Original Message-----
Is your ADO code trying to open the Connection with
exclusive locks
e.g. Mode=adModeShareExclusive? If so, instead consider
locking the
*data* at the row- or perhaps table-level rather than
locking the
database.

If someone else if doing this (e.g. another application,
a user
opening the DB in the MS Access GUI, etc), find out who
it is and ask
them to stop! You may need a different security approach
e.g. use
workgroups security so the database is only locked when
someone with
administrator rights actually needs to do administrator-
type things in
the database.

--

"Marius" wrote in
message ...
Hi everybody !
I made an Excel sheet that is reading from an Access
database (using ADO)) located on other computer in the
same workgroup.
From time to time, when trying to open the ADO
connection
it reports an error (no. -2147467259) saying that the
database is open exclusively...
To overcome this situation my solution is to manually
display the source folder content using Network
Neighborhood - then the connection can be opened
normaly,
without error.
Do you have any solution to avoid such problem.
Thanks in advance !
Marius
.