You will get slower performance with the file stored on the server instead of a local drive.
If two users try to open the file directly (not using open remote...), there is at least some chance of damaging the file, I'm told.
It would be better to keep the file on your local drive and use a script that saves a copy to your network drive for back up purposes.
Basically, Filemaker sucks at accessing files on shared drives. It still won't even backup to them.
A client side script that uses Save a Copy as... will back a file up to a networked drive.
For a server scheduled backup, you have to use a system script run from the OS to copy the files to a networked drive.
Thanks for the replys. I finished the database and it has been in use for a few weeks now running off the network drive and has been working ok. It's for a small company where it's unlikely there would ever be more than 3 users at a time.
Is the best way to do the network backups from a locally stored copy a script that saves a copy on exit? Or could I make a script that does it automatically throughout the day?
You can do either or both.