Where is the database located? On your machine? Is it shared with other users? Which version of FileMaker Pro are you using?
It's not recommend to used a file that has been recovered. Recover is used to make the file readable so you can export your data out into a backup copy without the issue. You need a backup from before the first time the message appeared. You need your own backup of files you use, separate from corporate. Backups can save the day. I backup to dropbox.
There is a "Save A Copy" Script step that you can add to a exit button so it will automatically backup each time you exit. Set a variable with your document path and add a timestamp to the filename, then every time you exit you have a new backup on your computer.
Sorry, recover is about your only choice.
It important to figure out what cause your file corruptions, so it does not occur again.
The database can only be shared with FMS or FMP and the database should be remove from virus scans.
if you google filemaker corruption you will see a wealth of information on how to handle the condition.
Once you have corruption in a file it is difficult to correct and the only 100% sure ways to fix the problem are to restore from an uncorrupted backup OR completely rebuild the file from scratch.
From scratch means start from a new, blank file and rebuild everything. Do not import anything but DATA from the corrupt file.
A recovered file should NEVER continue to be used but should only provide a data source.
Once you have restored the4 file your not done because you really need to perform a root cause analysis and implement the resultant mitigation plan.
Some system level event cause the file to become corrupt.. most likely causes are power loss while the file is hosted and being accessed.. and any external process ( virusscan, backup, dropbox.. etc ) touching the file while it is open and hosted.
if you dont eliminate the cause this will happen again.
It also sounds like you should adjust your backup plan.
The database is located on my computer and the information that is stored is pulled from our company server. Filemaker is installed on three other computers with read only rights. My computer has the admin. rights for the program. I am using FMP 12.
Thank you so much for the information schamblee. I started this database 5 years ago and it has been a work in progress through pre-construction, construction and now operation of our plant. From what I understand now, I may have to rebuild everything and can only use the recovered file as a reference of data? I am by far not an IT expert and was relying on someone that I thought had enough knowledge to set this up correctly and have dependable backup information.
Thank you for your input. I will forward this information to our IT technician and see what can be done. He said that the offsite backup lasts only about 30 days because of the size of the file. I don't know if there is anything available past @30 days that is a clean backup without the current issue that I am having. I have been able to use the program with minimal issues, but I don't use it on a daily basis. I could get the program to open by running a consistency check, but when I opened my log file, it appears that it never finishes the operation, therefore causing it to try and run the next time I opened the program. It finally came to a head yesterday when the recovery option didn't even work.
It would help to have a bit more detail:
- How big is your database file ( Mb, Gb ? )
- Do you store images or documents in Container fields ?
- Recover Step 6 rebuilds the Tables. A corrupt Table could make it freeze
- Is there a Recover Log ( it should be in the same folder as the db files ) ? Read thru the log ( or send it to me ). It is cryptic, but provides many clues, e.g. it might show which Table it stopped on, so you could perhaps delete that one table
- are you running FileMaker Server Software ? It is not clear, from your description
- For more info on file corruption, have your IT guy read thru this:
> When this issue first started, I could close this out once or twice and then the database would open with no issues and not data lost. Yesterday when I logged in, I got the same error and used the Recover command. It went through the process of recovering and snail speed. It got to step 6 of 17 and froze
Database file size: 7.07GB
I do store .jpeg in a container field
I don't know if I am running Server Software or not. If you can tell me how to find out, I can let you know.
I have had my IT person helping with this, but he is more network knowledge than software. It has been very frustrating. I know how to use Filemaker and create databases. Troubleshooting is not my area of expertise. When I opened the recovered database, it showed that there were 0 of 0 records found, but it still shows the file size to be 7GB. I searched for a drawing number that I knew should be there, and it came up. I am now having trouble knowing that the information is there, I just can't make it show up correctly. I was going to try and export the old file into a new one, but I am having a hard time doing that as well.
Any help is greatly appreciated.
Also, if I want to send you a PDF of the recover log, how would I do that? I do not see an "attach" option here in the reply area.
Send me a "Message", and attach your Recover.log file
No need for a PDF
> I want to send you a PDF of the recover log, how would I do that?
0 of 0 Records, while the Records are still there. I have seen this happen. Very frustrating
The Recover Log may have a clue
In the mean time, try Save a Copy as Compacted. It may take a long time, but can fix a multitude of problems
Just out of curiosity, download a demo of FileMaker 14 or 15, and try opening a copy of the file with that, and also see what Recover does
you may need to contact Tech Support
Since you are on FileMaker 12, you could consider using "external storage" of your container images, to keep your database file size down. But that is an issue for another day
Since you are Recovering the file, it is probably not hosted with FileMaker Server. Another thing to consider, later
Corrupt images in container fields has been known to cause FM to crash.
Get all the backups you can get. You may have to make a few different attempts to recover you data.
Unfortunately, the Recover Log does not say much, since it did not finish
It stopped on the "Table" Table, which is probably your main Table
Since the file failed the Consistency Check, Save a Copy as Compacted might fix that
Save the Original file ( if it will open ), not the Recovered Copy
If the Original will not open, then use Recover, select the "Advanced Options", and select "Copy logical structure (same as Compacted Copy)"
This might work