Thanks for the link. Helped to understand that its not my configuration, that others have also the same experiences.
I could not see a solution, is there a solution to it?
For me, there was a temporary solution.. but unfortunately it's not going to be a solution for most.
I was able to roll back my Windows 10 install to Build 10240 (pre Nov update), however I think the option to revert to a previous build only remains available for 1 month after installing the update. Since there have now been a couple (not inc security patches) I don't think it will be possible for others to do the same. I first noticed in Nov and rolled back days after. I then began testing on a secondary machine, which is now stuck on the latest build. Also, its only a matter of time before the next patch is pushed through... so I'm not sure how long I can remain on build 10240
Thankfully FMI have been able to reproduce my instance of it, which hopefully allows them to find the cause. So I guess it's a case of hoping for a patch from either MS or FMI, or both, depending on the actual cause.
Hi Steve and Setven_fl,
have a look at Re: Font issue FMPA 14.0.4 after Windows 10 upgrade.
The November update broke some functionalities in FMP 14 ( the link is about strange characters). The guy said that KB3124200 solved the character issue, may be it will also solve the Workspace issue.
It solved the character display issue for me, but not the crashing, but its worth a shot for Steven_Fl.
In my thread on the issue: Re: FMPA 14v4 or Win 10 (v1511) - Character problems in script workspace
which started out with the font display issue, but moved on to crashing, you can see I have tried all the updates, even a 'reset' of W10 10.0.10586 and also the very latest insider build (on fast branch) 10.0.11082.
But for me at least, only W10.0.10240 (pre nov) is stable, extremely stable. Luckily, my primary dev machine is running that and I am able to defer updates on it. I will be keeping an eye on my 'test' machine as updates appear (insider previews) in hope that one of them fixes the issue. Clearly MS has changed something.
Hello Steve and Steven and hello to all others
I have some of the same issue under Windows 10, when I am trying to create and save a new script. Than FM Pro / Pro Advanced crashes. If I do changes in existing scripts, everything is fine.
And this seemed not effected, when i start with an empty Filemaker Database file.
All those i've tested under Mac OS/Win 7, single/Server etc. There is no problem.
In my case the crash is unique to FM and Windows 10 (included actual MS updates)
Workaround: Creating a new script from the Dialog out of layout mode, it works without crash.
Hope it will help you
Thanks for the input. I see it happen when I have on saved scripts and the do crtl D or crtl L before I save the unsaved script. If I save it before doing something else it seems not to crash.
For sure it is an FM issue on Windows 10. I work on the same file at the same time also on a Windows 7 machine and never have an issue there.