Are you double clicking the icon for the file or the icon for the application?
If double clicking the icon for the file, try the icon for the application to see if the issue is with your file or the application.
If it's the application, you have bigger problem. You may need to reinstall, but first try to rule out other causes such as recently installed or updated software and such.
If it's the file, try launching FIleMaker, enabling the script debugger and then opening the file. If a script pops up in the debugger, cancel it and see if that lets you get the file open. If that does not work, try running a recover on the file and see what you get from that.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- 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.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).
Thanks Phil, got it to open now and I'll just copy those important changes to my backup copy now. Thanks again!
If you are copying structural parts of a damaged file to a backup, you risk copying the damage along with the copied "part".
I recommend testing the copy thus produced with a recover. (and it's much more work but safer to recreate the parts.)