scripts altering themselves on server system

[stanley]

We're running a multi-platform network with a dozen machines (mac/win) accessing FM Server on a Mac host. Everything is 5.5

The client machines all have startup scripts - they open the appropriate file on FM Server, run an appropriate script, and then the user is wherever that user should be. On the win machines, this is fine. On the Macs, there are times when the script for some reason cannot find the host (we've had all sorts of power problems during construction, so routers have been down, etc, but not the server) and then the client scripts rewrite themselves so that the "open" statement which pointed to the remote DB now points to the DB holding the startup script on the local machine. The "perform script" step which pointed to the remote script now points to the (only) script on the local DB (which is just a placeholder for the startup script.)

This is driving me crazy. Does anyone have any ideas?

-Stanley

[falkaholic]

Redo all the Perform Script steps and any Open Steps.

I have found that those steps cache the file names wrong sometimes, try clicking name of the databse in the step step (in the mail part) and if it doing the cacheing, and IP will show up. All you have to do is redo that step.

[Fitch]

When you use an opener file, you should always trap for errors. That way, if the server is down or otherwise unavailable, the opener script won't get broken. E.g.

Set Error Capture [on]

Open [network database]

If [status(CurrentError) <> 0]

. Beep

. Show Message ["I'm sorry, Dave, I'm afraid I can't do that. Try again?"]

End If

If [status(CurrentMessageChoice) = 1]

. Perform Script (this same script)

Else

. #do something else

End If

[stanley]

Yes, that's it. I had tried putting in an error capture, and noticed that it prevented some of the damage. Your way, however, is a more complete solution. thanks.

-Stanley

[falkaholic]

Actully, a similar thing happened to me yesterday, my networked system went nuts and said the all the script couldn't be found, i restarted the client and everything worked fine afterwards.

I'd take a closer look at the client machines.