Timed Compact and Repair

[Alejandro]

I have some people using an app that has a front end that links to another
database that holds all the tables. Recently they called me because the app
wasn't working and after some digging I found out that the problem was that
the back end needed being repaired and compacted. Now, to avoid these calls
AND me compacting that database manually every other day I was thinking on
somehow triggering the compact and repair function automatically.

One thought was to save some code in the back end database that compacts and
repairs it at, say, 1:00 am, when nobody is using it. The problem there is
that if the database is not open I don't think the code can be triggered.

Another thought was to trigger the compacting action when the last person
using the front end closes the application, so in other words the back end
would be compacted and repaired every time the last person using the front
end closes the app.

The thing is, I have no idea if these are even plausible options, and if
they are, how to implement them. I would appreciate any tips on how to do
this even if it is by using a method other than the ones I mentioned above.
Anything that repairs the back end every so often without me having to do it
manually would be just fine.

Thanks!

 

[Brendan Reynolds]

I have some people using an app that has a front end that links to another
database that holds all the tables. Recently they called me because the
app
wasn't working and after some digging I found out that the problem was
that
the back end needed being repaired and compacted. Now, to avoid these
calls
AND me compacting that database manually every other day I was thinking on
somehow triggering the compact and repair function automatically.

One thought was to save some code in the back end database that compacts
and
repairs it at, say, 1:00 am, when nobody is using it. The problem there is
that if the database is not open I don't think the code can be triggered.

Another thought was to trigger the compacting action when the last person
using the front end closes the application, so in other words the back end
would be compacted and repaired every time the last person using the front
end closes the app.

The thing is, I have no idea if these are even plausible options, and if
they are, how to implement them. I would appreciate any tips on how to do
this even if it is by using a method other than the ones I mentioned
above.
Anything that repairs the back end every so often without me having to do
it
manually would be just fine.

FMS sell a product that does that and a lot more. I tested a previous
version and it worked well.

http://www.fmsinc.com/MicrosoftAccess/monitor.asp

 

[Alejandro]

Thanks to all of you for your help. It looks like although it is doable as
David said, this task is beyond my capabilities. The app I'm referring to
here resides in one of my customer's servers and using this command code in
the task scheduler would imply having their IT crew involved and getting
permission to do that kind of stuff in their server...that's pretty much
mission impossible. i would still have to research that code David referred
to as I have no idea how to do that, but that would not be my main
problem...the problem would be the IT people letting me store procedures in
their server...

Thanks a lot for your help, though

A.
P.S. If you think you could help, I would really appreciate if any of you
took a look at another posting I have under "Access Database Forms Coding"
called "Graph not showing". This issue is really kicking my butt and I have
not gotten any posting from anyone in almost a week. I'm desperate for a
solution to this issue. Once again, thank you so much for your help.