DCRAPACCESS
asked on
Stable program
Hi Experts,
Right now i have a Access DB running as a Task Scheduler. In other words, i have a form with a timer that executes (opens other Databases and runs Macros) 24/7 365 days a year.
The problem is that this Access DB, is not as stable as i was hoping for. I have made a current solution that closes the database by killing it in the Windows Task manager if it has frozen for more than 1 hour. (Don't ask for the solution it is complicated to explain)
I was then thinking of making a Desktop Application in Visual Studio to replace my Access Task Scheduler.
My question is: would a Application programmed correctly in Visual Studio be more stable than Access. I need the program to run 24/7 and if it crashes it should restart. How would i insure that and is it possible?
Right now i have a Access DB running as a Task Scheduler. In other words, i have a form with a timer that executes (opens other Databases and runs Macros) 24/7 365 days a year.
The problem is that this Access DB, is not as stable as i was hoping for. I have made a current solution that closes the database by killing it in the Windows Task manager if it has frozen for more than 1 hour. (Don't ask for the solution it is complicated to explain)
I was then thinking of making a Desktop Application in Visual Studio to replace my Access Task Scheduler.
My question is: would a Application programmed correctly in Visual Studio be more stable than Access. I need the program to run 24/7 and if it crashes it should restart. How would i insure that and is it possible?
ASKER
Hi Gustav,
I have a lot of criteria before opening a Access DB and executing the Macros. So i would need a Program that i can trust running 24/7 and that is able to make a lot of tests before opening any database. I'm also controlling that the Access Databases don't crashes or ends i a loop and runs for more than 1 hour. So windows Task Scheduler is not an option as i see it.
I have a lot of criteria before opening a Access DB and executing the Macros. So i would need a Program that i can trust running 24/7 and that is able to make a lot of tests before opening any database. I'm also controlling that the Access Databases don't crashes or ends i a loop and runs for more than 1 hour. So windows Task Scheduler is not an option as i see it.
I see. The reliability of the running code would not change by this method, so if that is the problem, not the timer, then you will need something else to watch, as an Access app runs in one thread which cannot control itself.
That you could, I guess, solve with a .Net app with a "performer" and a "watcher" but it is a complete rewrite.
/gustav
That you could, I guess, solve with a .Net app with a "performer" and a "watcher" but it is a complete rewrite.
/gustav
>> would a Application programmed correctly in Visual Studio be more stable than Access.
I am not a fan of Access but if you introduce the same problem in you VS (C# or VB), you will the same issue of stability!
I am not a fan of Access but if you introduce the same problem in you VS (C# or VB), you will the same issue of stability!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Jim. This was not what I was hoping to hear, but what i expected. I will only run Office vba code i many different databases, so i will keep using Access, and work even more on insuring all possible errors.
Let it launch your Access app, start your processing from, say, the AutoExec macro, be done, and then quit Access.
/gustav