Although my dbs are hosted by our network server (NT 4.0), when users go to open the files, they get a message "The file was write-protected, you will not be able to make changes". I have moved the files into the same directory, one level up, and one level down from the Filemaker Server executable location, with no success.

To get around it, I have to close the service on the server, so one of the users becomes the host. I'm certain I'm missing something easy here; hopefully someone can enlighten me!

Are you opening the databases through HOST button?

I've tried it both ways... opening and Open Remote. Neither is successful.

Have you checked the properties of each file? On a mac single click on file when closed and get info. On Pc right click on the closed file and select properties. Make sure they are not set to read only. This may have something to do with your problem.

Michael

I only use Windows machines as clients, but on my Mac clients, the local file used to start the system is locked (read-only) on some machines, and the same message comes up when that file is launched. It is FileMaker's standard way of telling you that you can't use the database for anything other than viewing.

If you open the files on the server with a local version of FileMaker Pro (NOT via FM Server), does the same message come up? If so, it is in the files you are serving, as AudioFreak suggested. If not...

Warning sirens went off in my head when I read this in your original entry:

"To get around it, I have to close the service on the server, so one of the users becomes the host. I'm certain I'm missing something easy here; hopefully someone can enlighten me!"

This makes it sound as though you've got the databases on your clients. If so, you'll run into all sorts of problems... The one problem with FM Server is that it has a hard time telling the difference between one database called Clients.fmp and another with the same name, no matter what the location...

-Stanley

If a copy of a database needs to live on a client computer for reference, such as at home working late as a lot of people do. Might I suggest rename the database and change the file extension to FP0. This will at least change the Title bar letting you know you are in the client copy and not the served file.

Thanks for the suggestions, but here's additional info:

1) There are no db copies on clients, nor do I want them there

2) FMPro is not installed on the server

3) File attributes are not Read-Only or Archived

So my workaround is that Server is not being used at all, and everyone becomes a client of the first user logged on.

Call me,... I'll try to help you through this problem...

er... Email me and I'll try to help you out.

Clark...

My bad Anatoli...

You are asking for troubles... It doesn't pay to ignore the rules