Any update on if Filemaker is going to fix this Adobe Font bug that is wreaking havoc on all of my clients? I am getting so many complaints that the fonts on the interface are in wingdings everytime someone prints an Adobe document.
Is it really specific Adobe Fonts that is the problem. There was a problem with older fonts that have been addressed in FM16.
Else here are something to read
The issue is still affecting Ariel font in the latest version of Filemaker when being viewed in 100% zoom.
As I mentioned I am receiving complaints every day. This does not seem like it should be that big of a deal to resolve from an engineering standpoint and its been happening for a couple years now. PLEASE WAKE UP FILEMAKER!
Move this to Product Issue
Report a Product Issue
I've had this problem, I found that disabling Windows Font Cache Service solved the problem.
Disabling "Windows Font Cache Services" is something that's not recommended by Microsoft. They say that WFCS is an essential part of the Windows GUI and may cause the computer to seriously slow down, when disabled.
There are 2 other options that may help resolve this issue and both are embedded in the attached file. It is a windows-script that removes all files from: AppData\Local\Temp\acrord32_sbx\ and empties/removes the windows font-cache in C:\Windows\System32\FNTCACHE.DAT
Run it at your own risk! You have to run the file as local-admin and it will immediately restart your PC, so make sure everything has been saved before you run it. Run it at your own risk!
And no guarantees
I appreciate all the responses. Unfortunately these do not address the issue within all the 3 aforementioned versions of Filemaker. Adobe released an update on 11.15.17 that is causing this problem. There is obviously nothing that was corrected within Filemaker's previous patches that prevents this from still occurring.
FMI blames the issue on Adobe and Windows fonts, so there most likely will not be anything done.
I had the issue occur with two of my databases. I manually changed the font and the issue has not reappear. I still use Adobe reader and I still have Window font cache enabled. The only software to have issue with fonts was FM.
In the past two week I have had several clients report this issue.
Nearly all are first time reporters of this issue.
This take time to support something that is not due to the developer but we are the first called.
When we say it is an Adobe/Windows issue that is not a good or acceptable response.
The solution of a total machine restart is very cheesy when it is used as solution to an issue.
Sounds very "Windosie" and of course it is.
This is not a new issue but has been raising it "fangs" for several years and FM versions.
The "devil" is in the details.
If there is an issue within my solution a restart does not fix it, but wished it would.
This is bad image for us as developer because it is our issue when viewed from a client.
Retrieving data ...