Begs the question why you want to do this...
But: FM has an ActiveX interface that you can use to close FM gracefully instead of killing it. Do a search in the FM help for "activeX"
>>>begs the question why you want to tdo this...
Have a "FM robot'" machine gathering data after hours; we want to gracefully shut down and transmit the *.FM12 files elsewhere without corrupting the files.
Hm...will look into this, many thanks!
Taskkill will leave the files in a dirty state if the files were not closed before you kill the process.
FM's scripting has the ability to close files and exit the application; does that not work for you?
That's what I was worried about... so won't pursue that avenue. I appreciate the heads up on that.
>>scripting, close and exit.
I'm thinking -
Flush Cache To Disk
So, if this could be run without user intervention; i..e from ActiveX, that would be ideal.
I have used taskkill before with great success. There's a computer which automatically imports a few hundred thousand records each night into multiple tables across two files. Occasionally, the client would open the database the next day to run reports and forget to close the file or exit FileMaker. The only solution I could come up with was to use taskkill to exit FileMaker (whether it was running or not) before launching the data collection task.
This isn't a hosted file. It's a single solution running under FMP 11. It's been running for well over a year now without any issues. I certainly wouldn't recommend doing it, but it does work and hasn't caused any problems. There hasn't been any data corruption and the last time I checked, one file was over 6 Gb and the other was over 12 Gb.