Please help - Unsolvable Reference Libraries Problem

[kchernak]

I have an access97 db (HMDA.mdb)I created that is used by folks in various locations to enter cutomer data. It's not that heavily used, perhaps a dozen records a month or so, but the number of potential peaple who might enter a record are perhaps a few hundered, and they're located in separate locations across a dozen states or so. The db has worked pretty well, but come to find out that the user's PCs are not all uniformly configured. This has caused a few problems that so far I've been able to resolve after manually walking folks through various steps over the phone to determine where the problem originates. Generally the troublesome problems are associated with reference libraries - no DAO 3.6 (appears not everyone has it) so switched to DAO 3.5. The db auto tests for a mousewheel.dll and if needed, copies it and registers it when 1st time users need it. However, I now have a user who after walking her through various manual steps to check for libraries, setups, etc, and manually copying and loading the mousewheel.dll, she still gets a MISSING error when the db loads.

I created some code that will list the loaded and broken references in the db, but for this to work, the code needs to run in the db that has the problem.

So I'd like to create a separate diagnostic db (diag.mdb)will bare bones reference requirements that could be run by anyone with the minimum standard reference libraries (vba322.dll, MSACC8.olb, stDole2.tbl), that would check the users PC for available/loaded/broken references (and maybe more) associated with the remote HMDA.mdb.

Can this even be done?

Thanks!