If you launch fileMaker without attempting to open an existing database file, can you get FileMaker to launch?
Yes, I can get FileMaker to launch by using my desktop shortcut or on the Start menu, but often I have to shut down my computer first and restart, because it often freezes in the middle of the launch. But even after getting it to launch, the database file won't open or freezes in the middle of opening.
Yes, I can get FileMaker to launch by using my desktop shortcut or on the Start menu, but often I have to shut down my computer first and restart, because it often freezes in the middle of the launch.
I'm trying to determine if the problem lies with your file(s) or with your computer. Need to be very specific here: Does that sentence that I quoted here mean that it sometimes freezes when you try to open FileMaker without opening a database file? If you start up your computer, launch just the application, does it always launch successfully or does it sometimes freeze up on you?
Yes, it sometimes freezes when I try to open it without opening a database file. It freezes on the white square box at the very beginning that says "Initializing". If I launch the application right after TURNING ON the computer, it launches successfully most of the time, but still sometimes fails, but if I try it after just a restart, it seems to fail more often.
Sounds then like there's an issue with either your computer or your installation of FileMaker.
You might try temporarily removing all but a few basic fonts such as Times new Roman and Arial from your system and see if it affects how files open. (Initializing fonts is a big part of what's going on at the moment it is freezing on you...)
You can also try re-installing FileMaker to see if that helps. Make sure that you uninstall before you re-install...
Have you run a check disk on your system to confirm that the hard drive is healthy?
Note: assuming you get this figured out and can get Filemaker to launch (without opening a file at the same time) consistently, you may find that the many forced quits you've done has damaged one or more of your files. You may need to perform recovers on them to see how they check out.
Things to keep in mind about Recover:
- 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.