Ok but I think the approach sounds strange. ADODB does use ODBC if you
specify that driver. It just seems to me you are trying to replicate a
UI function when you should be programming a solution. But hey
sometimes one just doesn't have enough time.
I would create a master access db which holds the list of production
mdbs in it. You can also use Excel to retrieve and update the table in
Access. Maintain this one Access db with the mdb file names and
locations to pass to the application when the user selects it or the
application needs it. This way you never need to maintain the client,
just the master mdb file. Just my two cents...
Mike