Thank you for your post.
First, I have not encountered this type of incorrect state, and I don't see any similar issue reported.
Do you have any plug-ins installed? If so, which plug-ins? If you temporarily disable the plug-ins, do you encounter this issue?
When you get into this strange state, are you able to select other applications? The next time this occurs, launch Activity Monitor to see how much memory FileMaker Pro is using. This may provide a clue.
Are there any dialog windows active?
Thank you very much for your timely response. I appreciate your pointers of what to check to troubleshoot my situation. I would be very hesitant to return to developing in FM 15 Advanced if others were reporting the same situation, but since there are not other occurrences, I will and will make frequent backups....
The only plugin I have/had installed is: BaseElements;3.0;Enabled
I was able to select other applications when in the state.
There were not any dialog windows active, but I think there were a couple files from 1-2 other unrelated solutions open at the time (but am not positive about this).
I will post again if/when I have the incorrect state happen again.
Thank you for the additional information.
BaseElements plug-in is fine.
Being able to select other applications means this issue is probably FileMaker Pro related and not system related.
Having "1-2 other unrelated solutions open at the time" is fine.
If the issue occurs again, launch Activity Monitor and make note of the memory used for FileMaker Pro. Go to Force Quit and see if FileMaker Pro is displayed with "(not responding)". Lastly, write down as many actions as you can recall just prior to getting into the bad state.
Thank you as well for your additional guidance TSGal. I went back to working in FileMaker 15 today, so I will do my best to keep track of the information you requested if/when it would happen again... and I hope it won't... I hope that was a fluke!