Are you printing from the File menu or performing a script to print?
If you are printing from a script, try updating the printer setting inside your script.
If you are printing from the File Menu, try recovering a copy of your file and see if it prints correctly. If it does, you might try using advanced recovery options to:
Copy blocks as is
Deleted Cached settings
with the original copy of your file to see if that also fixes the issue. If it does, that file is pretty safe to use. If it does not, but the original recovery does, you would be better off replacing your file with an older backup copy if possible.
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).
Thank you for the post.
PhilModJunk is correct that file corruption is the most likely cause since only a single file seems to be exhibiting this behavior. However, what is the installed version of FileMaker Pro 11 Advanced? I've seen similar reports from user's running FileMaker Pro 11.0v1.
If not already using FileMaker Pro 11.0v4, then the suggestion would be to test with the updated version.
If the most up to date version is already installed and this issue still occurs, then the suggestion would be to follow the steps outlined by PhilModJunk.TSFalconFileMaker, Inc.
Thank you very much for ur concern.
Is there any solution except creating the scripts?
Thank you for the reply.
While I cannot guarantee a resolution, in the past running software updates for FileMaker Pro from 11.0v1 to 11.0v4 resolved similar issues. If not already using FileMaker Pro 11.0v4, then the suggestion would be to test with the updated version. The instructions and download for the free update are available here:
Please let me know if the issue persists when running the most current version of FileMaker Pro 11 software.