Sheaferm

#!/bin/sh /usr/bin/fmsadmin stop the above run as a shell script will shutdown the databases (giving clients 30 seconds to disconnect, by default) and stop the server. if you need other options (messages to clients, more/less time before disconnect, etc.) type fmsadmin HELP stop at the command line on your server. just put the two lines at the top in a text editor (make sure it's text only, not RTF or something), such as vi or BBEdit. call it somethign like shutdown.sh, then, at the command line, do: chmod +x shutdown.sh to make it executable if you need to make it a double-clickable type file (I'm not sure how applescript works and what it needs), call it shutdown.command, then do a command-i (get info) on the file, check hide extension if you want, and change Open with: to Terminal. -rich

err, not under Define Database. under Define: Accounts & Priveleges I have this working in our office with about 40 databases. all the employees have their own username/password authenticated against the LDAP server, then I defined groups for access levels on each database. the exec on a particular account (and maybe a couple of others) will have full access to their own client's database, then some of the administrative assistant types will only have data entry access. if you're not in a group that has specified access to a specified database, then you have no access. I hope you can understand these posts. I can hardly make heads or tails out of them and I wrote them. -rich

no, it's not necessarily needed to get authentication to work, but it's just to keep everything matching up. what I forgot to ask (and stupidly assumed that the answer was yes) was do you have your users/groups set up on the LDAP server, and are your databases set to authenticate from a remote server? for example: to authenticate from a remote (OS X) server using LDAP, you need to have a user "Admin" (which you can create with the Workgroup Manager). I would recommend keeping the user "Admin" though just authenticated via filemaker, then make a user for yourself, like "Joe Blow", put joe blow in the Filemaker Administrators group (call it whatever you want, but you'll have to make the group), then under Define Database in Filemaker, make a new account, authenticated from the remote server with an access level of Full Access, then type in the group name that you want to have administrator access, then you can just log in to that database with your own username/password of Joe Blow. -rich

under Filemaker --> Preferences you should have dc HostnameOfLDAPServer dc DomainOfLDAPServer dc TLDofldapserver ou NameFileMakerIsRegisteredAsInLDAP so, if your ldap server is at ldap.example.com and your server is registered as Filemaker you would have (in Filemaker Preferences under the LDAP Directory Service pull down menu) server address: ldap.example.com ldap port 389 Search base: ou FileMaker dc ldap dc example dc com Then in Configure --> Directory Service in Filemaker Admin check Register Filemaker server with a directory service Directory Server Name: ldap.example.com Distinguished name: filemaker.example.com and you can choose to put in the optional information if you would like make sense? -rich