So below is my issue. I share my database with my desktop from my laptop and this is what is returned. The data and layout look fine on my laptop, but are obviously messed up on my desktop. What can/should I do? Thanks!
At first glance it looks like it could be a font issue. There may be a font used that is not on your desktop machine.
It appears you were right, but in an odd way. I use Arial as the default, I have it on both of my computers. But for some reason the font showing up is "Z@RD1BF.tmp" rather than any sort of font. In the picture below, you can see where I changed "History" back to its original Arial, so it's no like there's really any issue. Only the odd TMP conversion.
There was another post recently reporting a similar thing. Probably worth checking it out:
Font Changes on Layout
Thank you for the post and responses.
Keywords is correct about the previous reports:
Possible work arounds include:
-clearing font cache file (C:\Windows\System32\FNTCACHE.DAT) and rebooting
-change text or theme
-use a magnification other than 100%
We are still attempting to reproduce. If anyone could provide the FNTCACHE.DAT file from a “problem” machine, or if you have further information on reproducing, please let me know.
Additionally, I forwarded a report to Testing and Development for review.
I upgraded an older Windows 32bit pc to Windows 10 and it corrupted my FMP12 install so I had to reinstall FMP12 to correct the issue. Have you just updated this problem machine to Windows 10?
Have you tried re-starting the desktop computer? Re-starting fixes a lot of things.
One person in our work group recently updated to FMP14 and Windows 10. When he views screen at normal 100% font, it is very garbled. Looks like image below.
However, if he increases size to 150% or reduces it to 75%, then it is normal font, but neither one of those are the screen size he wants to work with. The layout is set up 100% in Arial. I am thinking that this has something to do with FM14 and Windows10, because another user who has FM14 and Windows 7 is not experiencing this issue.
I have a copy of the FNTCACHE.DAT file that you requested from the user who was experiencing this difficulty. I have attached it to this message.
Documentation has been released on this issue, which includes our current Work Around. See Knowledge Base Article #15419. When more information is available, I will post it to this thread.
Has this been resolved yet? It is also happening with FM16 on Windows 10. Is there an update somewhere?
Corrupt index files can cause garbage records or corrupt Windows font.
See this link for corrupt font FileMakerPKB
to rebuild index
run recover with advance options
Sadly, this hasn't been fixed yet. If you do have a copy of your cntcache.DAT file, can you get that to us? We are still collecting those files when cases like these come up.
Retrieving data ...