1 Reply Latest reply on Nov 17, 2011 10:34 AM by philmodjunk

    Not finding a record and not saving new information

    HelenMartin

      Summary

      Not finding a record and not saving new information

      Product

      FileMaker Pro

      Version

      10.0v3

      Operating system version

      OSX 10.6.8

      Description of the issue

      Does not find a record when 100% the record is in the database.  Also does not save new changes to a record.

      After cancelling window that says it cannot find record a new window pops op.
      File name is damaged and cannot be opened. Use the recover command to recover this file.

      Steps to reproduce the problem

      Went to recover and recovered file. See below

      This did not solve the problem the file is still not finding records or saving changes to record.

      Expected result

      Expected to find some issues but none found

      Actual result

      Came up with message:

      Exact text of any error message(s) that appear

      Recover built a new database without detecting any problems. The new database is safe to use, though you should monitor the results carefully and make sure to keep up to date backups of your database.

      Recovery Result
      File block: scanned and rebuilt 241 blocks, dropped 0 invalid data blocks.
      Schema: scanned fields and tables, 0 items modified
      Structure: scans: 0 items modified
      Field indexes: rebuilt

        • 1. Re: Not finding a record and not saving new information
          philmodjunk

          Things to keep in mind about Recover:

          1. Recover does not detect all problems
          2. Recover doesn't always fix all problems correctly
          3. Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.

           

          Other possibilities.

          I'd like to see a more detailed descritipion of the steps you took and the design of the layout where you attempted to perform this find. The error message: "[filename] could not be opened" suggests that fileMaker is attempting to open a second filemaker file. This is the file you should recover, not your current file--perhaps that's what you did here, but we need to be sure.