Jump to content

Search the Community

Showing results for tags 'corrupted'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type

Community Forums

  • The New Claris Platform
    • FileMaker Pro 19
    • FileMaker Server 19
    • FileMaker Server 19 (Linux)
    • Claris Connect
    • Core ML
    • NFC and iBeacons
    • Add-on Modules
    • iOS Shortcuts and FMGo
    • Save Schema as XML and Upgrade Tool
    • Java Script and the Web Viewer
  • Community Resources
    • Community Articles, Tips, & Techniques
    • FileMaker Marketplace Discussions
  • FileMaker Platform
    • FileMaker Interface Features
    • FileMaker Schema & Logical Functions
    • FileMaker Go for iPad and iPhone
    • FileMaker and the Internet
    • FileMaker Pro 18 Advanced
  • FileMaker Server Administration
    • Previous Version Server Discussions
    • FileMaker Cloud
    • FileMaker Custom SSL Certificates
    • oAuth and External Server Authentication
    • Zabbix Server Monitoring
  • Brain Food
  • FMForums Affiliates & Sponsors
  • FileMaker Classifieds
  • FM Forums Operations
  • FileMaker Friday Night Chat's Topics


There are no results to display.

There are no results to display.


  • White Papers
  • Infographics
  • Samples
  • Add-ons
  • FMGo
  • Solutions
  • Tutorials
  • Plug-Ins

Product Groups

  • Workplace Innovation Platform
  • Site Advertising
  • Development & Hosting

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start







Website URL




OS Version

Found 1 result

  1. Hello Everyone, We have a filemaker file that is damaged. When we try to recover it, filemaker suggests we stop using the file and extract the data. We however continued using the file anyway as it is a crucial part of the overall system. At the same time I started creating the file from scratch. The file itself is quite big, more than 100 fields and 800000 records. It's been around for about 10 years therefore the fields have just kept adding. These are the steps I followed to create the new file ; 1. Create a new filemaker file with the same name as the old one. 2. Create all the tables that were in the old file. 3. Create all datasources as in the old file. 4. Sort the old database fields by type and copy over all fields except calculations and summaries. 5. Create all relations from scratch; to be exactly the same as the old file. 6. Copy over all calculations and summaries to new file. 7. Check all look ups to make sure all fields referenced are valid. 8. Go through each layout in the old file and create new layouts in the new file WITH JUST THE LAYOUT NAME (So that scripts can be imported from the old file without losing references to layouts) 9. Copy all scripts from the old file in to the new one. 10. Copy all value lists from the old file to the new one. 11. Go through all layouts and copy all the layout objects in to the new layouts. 12. Import all records from the old file. 13. Test buttons and layouts to see if all fields and scripts are correctly referenced. I performed all above steps and I managed to create a fully functional brand new replication of the old corrupted file. I decided to take the file and test how it runs together with all the other files, I retrieved a back up of the entire solution, replaced the old file with the new one and started checking other files referencing the newly replicated file. The relationship structure shows that the file replicated is correctly referenced as a datasource but the fields matched within the relation are unknown or are incorrect fields. Refer to attached image. I am confused to as why this is the case, the filenames are exactly the same as the old file. Shouldn't the relations pick this up? I thought perhaps this is due to the order the fields were added to the old one. i.e. the creation orders. I then decided to take the fields off and copy them back in the same creation order as the old file, copy over the new file to a brand new copy of the solution. This made no difference, the external files were still referencing the wrong fields or were unknown. I am very curious as to why this is, I know very little about the internal structure of filemaker, I am pretty sure filemaker does not assign an unique id to each field. Even if it did, creating the fields in the same creation order should assign the same id as the ones in the older file. Can anyone shed some light on this? I am going to see what the replies are going to be before I put the new file live and rebuild the external relation references, which is going to be a lengthy process. Thank you in advance.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.