I had earlier inquired about inserting files in FM DB, see link below.
The following was suggested:
This problem can be alleviated by using a check-out//check-in system, where the user "requests" to export the document, and it is then flagged as "locked", so no other users can access it until the first user finishes with it and replaces it. This is a bit more complex to set up, but it's not unreasonable, it just requires some scripting of the user interface.
The biggest problem with storing the files in the database itself is how much this will increase the size of the database files and affect performance. If the files are mostly small, it may not be a problem, but if you're dealing with huge desktop publishing files, for example, it's probably not worthwhile.
I'm not worried about increasing the size of the database since it will only host files for open/active jobs (not more than 100 word or pdf documents). I'm looking for help with the "check-out/ check-in system" described above.