It's not quite that easy, I wish it were. To put it in some perspective, suggesting we fix all unhandled exception errors is like us suggesting that physicians just need to reduce all their patients LDL levels < 190 and no one would have heart attacks anymore. That's error is a basically a symptom...not the diagnosis. It also could be a red herring. It's not happening consistently everywhere and where it does occur it's not consistent on all workstations. We have never been able to replicate it here in house. All random practices and random workstations so we're looking for similarities. Program code does the same thing every time when executed. However it reacts differently with the environment in which it's running. It would appear to be pointing to the environment (server and workstations). The gdi32full.dll Error points to the graphics display interface. The code we execute can react differently with different versions of operating systems, how much memory does the pc have available at the time, maybe the workstation has its own graphic card with more memory, maybe it's some combination of events. Much of this is beyond my technical ability so I'm relying on others more knowledgeable but even they are stumped. We have a few thoughts and we have a team here sharing ideas and all the information we get from this board and the research the techs have done, and are doing, with our clients. We have something we want to try with Dr. Wilson and our techs are reaching out today
Last edited by cconrad@ac; 01/24/2020 12:16 PM.
