unmodifiable database after cloning

[dr.stitch]

My goal is to clone a database that is currently on our server. What I did was close the database, clone it offline, and reuploaded it to the server. Before uploading it to the server though, I made sure everything was working, including ability to modify fields, change account privileges, etc. However, after uploading it to the server, I lost all of this functionality. Could someone please help me with this? Thx!!!

[Fenton]

It's likely a Mac OS X permissions issue. When you move files to your own machine, the files' permissions are changed to yours. This is a problem with FileMaker Server database files, as they need special FileMaker Server permissions. But it's easy enough to fix. Select the files, Get Info. Drop down the Details view, at the bottom. Then change the permissions back to what FMS wants.

Owner: fmserver

read & write

Group:

read & write (tho I think read is enough)

Others:

read only

If you have several files, it's easier to use an app to do this on an entire folder of files at once. There are several, such as "BatChmod" and "iRepair", but I like "PrivilegeFix" (simplest :-).

[David Jondreau]

Shouldn't using the Upload function of Server avoid the permissions issues?

[dr.stitch]

That worked! I think the group name also has to be fmsadmin. Thx!