I have a routine that exports records every 10 seconds to a defined folder. This is part of a solution to keep an MSSQL database in synch with an FM database (and the the MSSQL tables have "triggers" (MSSQL triggers, not FM triggers whole other thing), which is why I cannot I cannot do this nice and simply via ODBC and the (awesome) Actual Technology drivers from FMSA11, which was the original plan.)
Occasionally, I get the "cannot write this file" error, which I am still puzzling out. That isn't such a big issue (for now, at least, I hope not) because the export script searches for a flag, exports the records as text, and then sets the flag to being "done," and the records will not be exported again once it has already been exported. My problem is that the Error Capture function in FM doesn't capture failed file exports. I need to ignore the failed exports and have the script keep cranking. If it hits a bump, it just stops, waiting for the error dialog to be confirmed. The script is running on a headless WIN client somewhere I won't notice a failure unless I go looking for it. Does anyone know a way to: Log the file export errors and then click "OK" on the error dialog so the script will continue to run. (I am Mac person, so if there's a WIN utility that does this, I'd love to hear about it.) TIA, Tom Langton
