8 Replies Latest reply on Sep 6, 2012 10:17 AM by philmodjunk

    FM database becomes "unmodifiable" on server

    MikeF_1

      Title

      FM database becomes "unmodifiable" on server

      Post

       

      Filemaker 11 Pro database file [fp7], shared on Max OS X server, it's own directory.

      No more than three people using it at the same time, all with licensed copies of FM 11 Pro.

      On an annoyingly regular basis, but intermittently, when a user attempts to open the file, it has "become read-only".

      Records cannot be edited - the message states this record is unmodifiable, the Print and File Options commands are greyed out, etc.

      There is a Time Machine backup that runs, perhaps it's locking the file?

      If anyone has ideas on this please let me know.

      Glad to send more detailed info if necessary.

      Thanks,

       - Mike

        • 1. Re: FM database becomes "unmodifiable" on server
          philmodjunk

          What is the exact wording of this message? Does it say that the Record is locked or that the File is unmodifiable?

          How do they access the file to open it?

          Do they use Open Remote or is this a shared directory where they use Open and open the file directly. The latter option is not recommended as it can damage the database file under certain circumstances.

          Time Machine shouldn't lock or modify this file, but if it is backing up this file while open, the backup copies it makes will trigger an automatic consistency check should you open one with FileMaker and could easily be damaged. Back Up software should not be set to back up open FileMaker files for this reason. You can set FileMaker Pro or FileMaker server to make a backup copy and then TimeMachine can back up this backup copy.

          • 2. Re: FM database becomes "unmodifiable" on server
            MikeF_1

             

            Believe it says the Record is locked therefore unmodifiable.  Can't get at the exact error msg right now because ...

            Went onto the server and rebooted Filemaker [not the server of course].   This alleviated the problem.

            So FM Pro can be set to backup regularly to another directory?

             - Mike

            • 3. Re: FM database becomes "unmodifiable" on server
              philmodjunk

              If it says "record is Locked" what you have is that one user has opened the record for editing and this locks out other users until the first user commits the record and thus releases it for others to edit. This is a necessary feature of shared databases as you will have any number of problems if two users are allowed to edit the same record at the same time. In this case, the message should tell you the user name of the client that is editing the record.

              If it says the "File is unmodifiable", then you have a user account permissions issue (on the computer, not in FileMaker) and it sounds like the wrong method is being used to open a file if you are sharing it.

              To save a back up copy using FileMaker Pro instead of FileMaker Server, you can use a script with Save A Copy As to save the current copy of the file to a designated location--even a remote volume--something that Filemaker Server can't do with a back up schedule. You can either set up a script that is performed when the file is closed to check and see if this is the last user to close the file and if so, it save the file so you get a daily back up copy at close of business or you can use Install OnTimer Script to save periodic copies throughout the day. You may find that this second option makes your file unaccessible for an unnacceptable lenght of time, however.

              • 4. Re: FM database becomes "unmodifiable" on server
                MikeF_1

                 

                As a first step, we have removed sharing of that directory other than Admin level, so when any user attempts to use File / Open they will be denied.

                Will let you know if that worked.

                Thanks Phil.

                 - Mike

                • 5. Re: FM database becomes "unmodifiable" on server
                  JimMac

                  Your users should never use OPEN on a shared database.  They should use OPEN REMOTE.  Timemachine only works at a Mac directory level for files modified since last backup.

                  Jim...

                  • 6. Re: FM database becomes "unmodifiable" on server
                    JimMac

                    oooopss.  I left out that is appears that Mac's permissions on that file are causing your "not modifiable" and not FMP.  That comes from using OPEN.  Do a Get Info [cmd I] on your DB and check permissions.  Sometimes these are messed up.  Use Disk Utility to repair permissions.

                    Jim...

                    • 7. Re: FM database becomes "unmodifiable" on server
                      JimMac

                      @Phil

                      A backup of a serial device like a hard drive is a snapshot in time.  If you make your back up or TimeMachine makes it, 4 microseconds later, it will be different and any changes you make will make after is subject to be different, if lost.  TimeMachine makes hourly backups, but you can click Back Up Now anytime you want.  so if you do heavy changes...

                      BACK UP NOW.

                      Jim...

                      • 8. Re: FM database becomes "unmodifiable" on server
                        philmodjunk

                        Yes but neither TimeMachine nor any other third party backup software should be used to make backups of open FileMaker files. The resulting backup will trigger a consistency check when first opened at best and at worst can be damaged and completely unusable.