RE: NoPrintDialogs Keeps Returning!
Jim,
To get back to your particular question regarding the monitors... yes I'm talking about physical displays.. In the old days when everyone had only a single 17" or 19" monitor, it was not a big deal to share the same DEX.ini, though it quickly became pretty big due to all the local printers that had been mapped from each users..
The day people started asking for a second (or third) display to work more efficiently, it started also to become an issue with shared DEX.ini's .. I've had users calling me saying that their GP wouldn't start anymore from the CITRIX server, but they could see the icon in the task bar... Now the trick was that GP was effectively started, waiting for user input, but users couldn't "See" it because it was off-screen.. As a previous user equiped with a dual-monitor setup had moved the main GP window to the second display, and closed GP from there, the DEX.ini was updated on exit with the X-Y positions from the window :
WindowPosX=132
WindowPosY=40
In clear, those values were sometimes negative and represented in Absolute Coordinates, the actual top left corner of the main GP window. Thus, all you had to do was to reset those variables to 0,0 and relaunch GP. Or you could also use the 'magic' trick to move the hidden GP window back to the main display by pressing ALT-SPACE BAR and select the 'Move' option from the pull-down menu, then use the keyboard arrows to move the window back in sight.
Nonetheless, this became a serious problem and that was one of the major trigger to individual DEX.ini files.
David added later on the SDT (and now GPPT) a feature that would make sure the main GP window could never be 'off-screen' from the physical display to avoid such issues, making the individual DEX.ini file less of an issue.
Hope this helps.
PS: Leslie Vail (and Victoria Yudin too I believe) has posted once a long blog entry about all the DEX.ini switches : https://community.dynamics.com/gp/b/gplesliev/archive/2014/02/20/dex-ini-switches-my-complete-list