As I understand taskkill, it kills all processes (same as Unix kill), but does not quit the application gracefully. So the on close script does not run, does it?
If true, no wonder the databases are not closed and hence corrupt, and consistency check runs therefore.
What happens here with this solution is a nightmare for data integrity, something that should never be done to a FM database.
The best solution would be to host the databases in FileMaker Server, which allows live backups and to run the server permanently. Tell them their data (and the time needed to fix corrupt data) is much more valuable than the money they have to invest for FMS.
Many thanks for the reply - I've already said to the company that they should really be using Filemaker Server - their argument is that their current solution works, and has done for the past x years, therefore they don't believe they should have to pay more!
I've just run a quick test on a Virtual Machine in my office and it appears to work correctly (as intended) -
taskkill /im "FileMaker Pro.exe"
SUCCESS: Sent termination signal to the process "FileMaker Pro.exe" with PID 2099.
Filemaker then gracefully shuts down and creates a copy of the file.
Therefore the question is - why is it checking for consistency, and why is it freezing during this check!
Many thanks again,