You’re offline. This is a read only version of the page.
2
Greetings,
I'm familiar with how the infamous NoPrintDialogs switch in the dex.ini works, but it seems no matter how many times I remove the entry or set it to NoPrintDialogs=FALSE (we want it to appear) it returns after some period of time.
We're on GP2013 SP2 and are having this on a single terminal server.
Any suggestion how I can get this setting to remain? I'm not using named printers, but I've read a few posts about configuring this is you do not want the print dialog.
Thanks!
Jim
*This post is locked for comments
Hi Richard
The Support Debugging Tool is now GP Power Tools. It is developed by me at Winthrop Development Consultants and sold via my distribution partner Mekorma.
The setting could be in both the system level Dex.ini and the User level Dex.ini.
If the User level Dex.ini is being used, that will take precedence.
While a user is not logged in, the Dex.ini settings are stored in the syUserDexIniSettings (SY01405) table.
I suggest looking in the table as well as the system level Dex.ini.
GP Power Tools can update System and User level Dex.ini settings automatically using the Dex.ini Configuration window.
GP Power Tools Portal: http://WinthropDC.com/GPPT
David
I'm running into the same issue. We are running off of a Terminal Server. (Windows Server 2012)
The flags have been set as recommended but are still having the same issue.
NoPrintDialog is set as in the dex.ini document provided.
I thought about setting the dex.ini to read-only but that would not work as certain items in the ini need to be updated, ex last user logged in.
We haven't tried the SDT (Sorry David) but would that be the last item? And if so would it keep that field set as a default and not change it?
Jim,
I just updated the Dex.ini file I have uploaded to Box. It's a Word document you can download:
app.box.com/.../xkgae2rz1vil1ap4o579
Kind regards,
Leslie
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
Hi Jim
Use Setting Exact Match mode with the setting as NoPrintDialogs and the Value as FALSE.
As long as you understand that this can have negative effects on Named Printers (which you said you were not using), then that is fine.
David
PS: Thanks to my #teammusgrave supporters, Leslie and Beat. I always love it when my tools are offered as solutions.
Hi Jim,
No, the way it works is that the variable goes on one line and the Value (TRUE) on the second line (see the PDF user guide of GPPT).
WOW - I got all the experts to respond on this one! Thanks for all the great responses (I've actually see most of your contributions on this topic in my search!).
To throw a few things out there that you've all touched upon:
Thanks again everyone!
Jim
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
