I am seeing this on more and more clients.

No one else is seeing this issue?

Any of the panels modified?

Some yes.  Some no (definitely not the daily transaction register print window)..

If this is happening on unmodified panels I would look at the number of monitors and the screen size, both of which are known to cause issues.

Thought about that too.   So far I have not been able to confirm a connection.

The fact that it seems to be random and fixed by a computer reboot tends to make me think there is not a connection.

Will just keep on gathering info until a pattern emerges.

Now that I think about it.  This started happening around the 19th which was the time when the year end IRDs were first released.   Some of my clients required installation of product updates and I believe they had UDFs.  Some of the screens did have UDFs on them (however that doesn't directly explain the daily transaction register window).

Client yesterday had an horrible problem with printing PDFs that we finally traced to needing to do an update in custom office after installing the product update.  It was not manifested by the usual errors one sees in this situation so it ran us in circles for a while.

At one point we so the above described situation happen there as well?  

Might be a connection?

This has to be something environmental,  because I just saw this happen in Federal E-filing and Reporting.

The plot thickens.   Beginning to look like an interaction between my remote support software (Teamviewer) and Sage 100 / Fed E-Filing ?   Updating the remote software for latest patches.   Hopefully that fixes it.

Since upgrading to Sage 2014 a few days ago, we are also seeing issues in different modules in Sage where fields of data and buttons are disappearing from panels (customer inquiry and sales order entry, for example), only when our IT Department remotes in to the user's workstation using TeamViewer.  Did the latest TeamViewer patch help and what version of Sage are you using? Thanks.

Good question.  I've been cheating and using the Teamviewer 9 quick support for a while and have not tested recently.  I will do the latest update and report back.

Looks it might be fixed with the latest Teamviewer update.

However,  the last time I tested I was using Sage 100 ERP 2014 (it might have been an earlier version)  and I tested with Sage 100 ERP 2015 just now.

Can't say with absolute certainty until I try it with a few other clients.  Also,  really don't know if it was a Sage 100 update or a Teamviewer update that did it.

Looks it might be fixed with the latest Teamviewer update.

However,  the last time I tested I was using Sage 100 ERP 2014 (it might have been an earlier version)  and I tested with Sage 100 ERP 2015 just now.

Can't say with absolute certainty until I try it with a few other clients.  Also,  really don't know if it was a Sage 100 update or a Teamviewer update that did it.

Just had the opportunity to test with a client using 2014.   I had no problems.