peeking into password protected mdb's

[J. Freed]

I've written a program that will extract ODBC information from an mdb file
(from MsysObjects). I've generated a list of some thousands of mdb files over
our network; the program links to them, extracts the MsysObjects table,
closes the link, then processes the contents of the copied MsysObjects table.
It seems to work well with one problem: if an mdb has an internal password
(which we try to discourage), the program comes to a dead stop waiting for
someone to either type in a PW or hit Cancel. As we plan to run this during
downtime and will take several hours, is there a programmatic way to "peek"
at an mdb file to establish that it's password-protected so the program would
know to not try to open it?

Also, if you think of other potential issues/problems with this methodology
(particularly with open files), I'd appreciate your feedback. TIA......

 

[Arvin Meyer [MVP]]

I'm not sure, but you might take an alternative method into consideration.
Add a timer variable that allows maybe 2 or 3 seconds than the longest
process time. If the process doesn't complete in that time, grab its
filename/path and save that to a log (or just log all the process times and
filenames) then move on to the next file.