I have two databases running on a Filemaker Pro Server 7 (Advanced) running on Tiger (10.4). On one of the two, I can access Scriptmaker and add user accounts remotely from my client to the server. On the other, I cannot, even though I am logged with an account name that is a superuser (full access).

I have copies of both on my machine for development (running Mac 10.3.9). And both seem to be set up the same way on my machine, and I have full access to both on my local machine.

What have I done that prevents full access on one (on the Server) and not the other.

P.S.

I think I may have exported records from the server and imported them to the local version (on the problem database) during an upgrade/enhancement cycle. -- Could that have done it? It so, Why?

You have to check the permissions on the file. The owner needs to be fmserver, and the group should be fmsadmin. Check the file that's working to make sure.

Dana

They're both "admin" and "fmsadmin". Does "fmserver" have a special implication?

Bless you, Dana. Three days of horrified hair pulling were solved by changing those permissions.

I work with hfinger and helped him remedy this issue. Due to the known permissions issue within FileMaker 7 Server, I started there. I tried changing the Owner permissions to "fmserver" for the in-accessible file and they persistently would switch back to "admin" upon locking the permission.

My solution was to change the "Databases" folder permissions to: Owner: fmserver and Group: fmsadmin. Once these changes were made the databases behaved as they should.