We've got a strange problem happening. On each client machine there is a DB in the startup items which automatically runs a script opening the appropriate remote DB, then runs a remote script. This works fine. However, every now and then these scripts alter themselves. (We've had electrical problems, power outages, etc., but it doesn't always seem to coincide.) What occurs is that the startup script suddenly no longer points to the remote DB and remote script, but rather points to itself. This only seems to happen on the Macs.

What it means to us is that the startup scripts are no good. I suppose the solution is to remove the scripts from the startup folders and require the users to click on an icon on the desktop, but I'm wondering if anyone has encountered a similar problem, or if I've just forgotten something simple.

thanks

Stanley

Yes this is a well known problem. Check Vaughan's post regarding opener files in the development standards forum. It was posted quite a while back (at least a year), but it covers all the bases and has a solution for the problem.

Use the Set Error Capture [on] step to stop FMP from posting the open dialog box when the database is off-line, and trap for the error yourself (show a message saying the database is not available, pleasee try later).

Thanks, guys. I hadn't noticed Vaughn's earlier post. It's a strange bug, though. Does FileMaker intend to fix this?

Thanks again

Stanley