This bug hit me when developing forms and queries in access 2007 when linking different data sources.
Unfortunately, there wasn’t any obvious cause and I had to rewrite the forms and hope/pray it worked second time around.
There is a kb article here: http://support.microsoft.com/kb/269495 which describes the common scenario which is 3rd party software causing the problem, but in my instance it was caused by access 2007
As with the previous problem, the software which crashes in windows also crashes on linux. Thus, I need a way to prevent it crashing in both systems.
Fortunately, the linux way is a simple bash script which essentially recursively executes the application. That is great for my app, but might not be if yours happens to run in a daemon or in some other manner that cant be executed from a script.
[code]
#keepalive.script
program_name
./keepalive.script
[/code]
It’s a sad fact of life that applications crash, even the most hardened and robust software eventually flips out. When that happens, its often preferred if the application can automatically restart, but for obvious reasons this functionality is not built into windows (who would want word to auto restart every time it crashed!). So I had a poke around the internet, and came across a little application called Application Monitor. This little tool does what you’d expect: it starts, monitors and then restarts software if/when it crashes. Anyway, if that sounds good to you, check it out! Now all I need to do is the same on linux
Powered by WordPress