I'm running FM Pro 4.1v1 to manage a database of four interrelated files. During the day there are often four or five users connected over the Internet (via port 5003, not using the Web interface), adding and modifying records. There is also an AppleScript running which does searches, sorts and data modification. And there's also the occasional Web access, which involves a search and data modification. All this is on an iBook running Mac OS 9.2.

The problem is that every couple of weeks, FM complains that it can't read the disk the file is on, and I end up having to quit and relaunch FileMaker. When I do, FM complains that the file is corrupted, and rebuilds it.

I know this problem has been bandied about in the past. What I'd like to know is if there's any connection between this problem and the use of AppleScript or the Web interface. I would assume that FM would properly handle concurrency control, but does anyone know if there were bugs in this area with FM Pro 4.1 that could be gotten around by using transactions or some other mechanism? Thanks.

Are you using FMP 4.1v3 and the latest version of Web Companion -- I think it's 4.1v6 but not sure.

Is the disk almost full?

Is the hard disk set to sleep?