Detecting if an Access Database needs repairing

[Slarti]

Hi, I support 30 or so distributed Access databases and often only find out one needs a repair when a User calls after 2 to 3 days. Is there a method I can use to detect when a dB has crashed? I can use the OpenDatabase method and loop through the dBs but I run into password problems if passwords change. Idealy I'd like to bypass the password request and look at the dB properties or something!

thanks, JH

 

[vb5prgrmr]

Unfortunatly ... no, but what you could do to help prevent this problem is to create a program that you can run every night when people are not using these databases which will compact and repair each database and create a log for you if it runs across any problems.

Good Luck

 

[koala15]

vb5prgrmr comments are to be followed but .... from a management perspective, why are the paswords being changed?

I would have thought that would have been your responsibility ... for example, (and this is being very dramatic) what would happen if a distant person changed a password at the end of the working day then got hit by the space shuttle crashing to earth?

Just something to think about.

"Life is full of learning, and then there is wisdom"

 

[Slarti]

Thanks for your replies people. I was just wondering if there was another way of doing this.