Filemaker seizes after inserting file into container
Description of the issue
Often a Hard disk must spin up before a file located on it becomes available to be read by a program. This delay can take about 1-5 seconds. BUG: When we upload a txt file to a container field in Filemaker, if Filemaker must wait for the hard disk to spin up, it seizes. Filemaker must then be force-quit, and we must then wait 2-3 minutes for the Filemaker server to allow us back in, or else it says we are in "license conflict" with ourself. Intel Core Duo, Mac OS 10.5.7. Filemaker Pro 9.0.3.