FileMaker Server has its own backup routines built in ("Scheduler") if you are hosting using plain-vanilla FileMaker Pro, quit out of the files and then do a manual backup of the database files at the end of the workday, then reopen them. Backing up live hosted files ALSO corrupts them. All the folks USING the file would get in by going File Menu ——> Open Remote ——> Favorite Hosts ——> input the IP Address of the host computer as a "Favorite Host" and select it ——> pick the file and hit the "OK" button.īy the way, disable any hard-disk-level backup software. They are allergic to it.Ĭ) FileMaker Pro, or FileMaker Server, should be installed on the host computer and the files that are to be shared as multi-user files should be OPEN and filemaker sharing enabled within those files. OS level file sharing corrupts FileMaker database files. Multi-user filemaker databases are properly shared by putting them on a computer that has OS level file sharing turned OFF meaning they are totally invisible from Network Neighborhood and etc. NOT on the server on which the file resides.ī) For a multi-user database, unless it is just a "for the moment / temporary" database that you aren't going to care about by June of this year, you do NOT put the database on your "main server" which I assume is a FILE SERVER where you can navigate to the actual files from your local computer. I just cant find it:argh:Ī) Privileges for FileMaker should be set INSIDE the file using Accounts and Privileges. What do we need to do in order to have each user with data entry access to their own database and read only access to all the other databases? I am totally lost and getting to the point where I am about to give up but I am sure that there is a way to do this.
The second user could access their own database in the data entry privilege set but was denied access to the other database. We set all the accounts and privileges and one of the users could access their own database in the data entry privilege set that we created and they could access the additional database in the read only privilege set.
We removed all databases and only had two in the folder. Each time we set this up we end up with someone not having access to a database. The staff person who is the case manager of each database has data entry access, the Admin has full access and all other staff should have read only access. We have granted permission for all users to access this particular folder on the server and set privileges for each database. We have all these databases saved in a folder on our main server. We have several staff memebers who use FMP8 for client databases.
0 kommentar(er)
