Dex.ini settings

(0) Share

Report

Posted on by Community Member

Hello all just wondering if anyone can help me with this question. I found and downloaded the Useful .INI settings document created by Leslie Vail. I found the following settings and believed them to be defaults which can be used rather then the dex.ini returning the last values for these fields at last login..

SQLUser=User_ID

SQLDataSource=Data_source_name

I want to ensure that when users log in they always get the above information rather than the last user and datasource.

I've put these into my dex.ini, but they don't work.

SQLLastDataSource=GP2013 R2
SQLLastUser=sa
SQLDataSource=EEEEE
SQLUser=AAAAA

*This post is locked for comments

All responses (8)

Answers (4)

Verified answer

L Vail 65,271 on at

Like (0)

Report

RE: Dex.ini settings

Hi Irene,

This is a new switch that I believe may only work with R2. Not for sure on that one since I only have R2 installed.

Kind regards,

Leslie
L Vail 65,271 on at

Like (0)

Report

RE: Dex.ini settings

Hi Susan,

I think I mentioned the Support Debugging Tool a couple of times in my response to you on August 7th. I'm glad that you have taken a few moments to get a taste for all of the cool things you can do with the tool. Be sure to install it on all of your workstations in order to get the .ini configurator to work.

Enjoy!

Leslie
sueconrod 337 on at

Like (0)

Report

RE: Dex.ini settings

I'm shocked that no one has mentioned the Support Debugging Tool which has a setting so that you can define the Dex.ini so that the last user does not show and the DSN can stay constant. This way when you have a shared dictionary or OLEPath that needs to be set to a shared location and can get rid of the print path filling up on a work station.

The only issue as a customer is that you have to get the debugger tool from your VAR, it is an XML program that needs to be installed on all workstations or in our case the Terminal Servers we use to access Great Plains. But it is free. And it can send a message when a user gets an error on the screen they can hit CTRL+D and it will capture the error message and you can set it up to send to one person who can then look at the error and make changes.

I love the Resouce Information. I can go to a window and find out who has security to that window. So, when I'm asked well who has access to that window, I can give Accounting that information immediately.

There is even a feature where you can change the colors for each company when you have multiple databases. That can stop a lot of errors.

Here are some of the features:

It can help you identify the specific series of events which lead up to an issue or bug in the code occurring.

It can be used to quickly and simply turn on all logging and profiling capabilities without restarting the application. This can be useful when looking at performance problems.

It can be used to find details about dictionary resources and other security objects.

It can be used to identify resources (forms, reports and tables) causing security access issues.

It can be used to enable and disable third party products or change the order of the products in the launch file.

It can be used to export data from and import to any table.

It can be used to run SQL or Dexterity scripts without needing Dexterity or SQL Administration Tools installed.

It can be used to capture and email or save screenshots of all open windows and a system status report.

It can be used to send email to the system administrator, even on systems without a locally installed Outlook client.

It can assist in resolving issues with reports using Report Writer (RW) user defined functions.

It can roll out Dex.ini setting changes to all workstation in a system.
Verified answer

Richard Wheeler 75,848 Moderator on at

Like (0)

Report

RE: Dex.ini settings

Can you modify the GP icon to execute a batch file to call GP? Inside your batch file you can copy a template DEX.INI file that has the username and datasource you want so no matter who logged in last that will be overwritten by your desired settings.
Verified answer

Community Member on at

Like (0)

Report

RE: Dex.ini settings

Hi Leslie, thanks for getting back to me. Your answer makes sense regarding the SQLLastDataSource and SQLLastUser. However, even though I'm using GP2013 I have not been able to get the EnableServerDropDown=FALSE to work. I will try reading through the SDT manual to work out how to force the User_ID and Datasource using that. Cheers and thanks again. Irene
Community Member on at

Like (0)

Report

RE: Dex.ini settings

Hi Soma, thanks for getting back to me with a suggestion. The SQLLastUser and SQLLastDataSource are overwritten next time the use logs in, so I would have to somehow save the dex.ini somewhere using a batch file and update it every time a user logs in to save it in it's original state.
Verified answer

L Vail 65,271 on at

Like (0)

Report

RE: Dex.ini settings

Hi Irene,

I hope your having fun with the Dex.ini list - thank you for downloading it.

The SQLUser and SQLDataSource switches do not work with Dynamics GP. They are Dexterity switches that you can use if you are developing a stand-alone application and do not create your own log in window. The SQLLastUser and SQLLastDataSource are the switches that apply to Dynamics GP. These switches are automatically created and updated by GP.

Below is a description of the switches you introduced.

SQLDataSource=Data_source_name

This setting allows you to define a default value to appear in the Data Source field of Dexterity's predefined SQL Login window. Dynamics GP does not use the predefined SQL Login window when accessing the SQL Server. GP has it’s own login window, therefore, this switch does not work in Dynamics GP. If you are creating a stand-alone application, this setting would work so long as you don’t design your own login window.

SQLUser=User_ID

This setting allows you to define a specific user ID as the default value to use in the User ID field of Dexterity’s predefined SQL Login window. This does not have any impact on the Dynamics GP login window, because Dynamics GP does not use the predefined SQL Login window when accessing the SQL Server. The native window looks like the login window you may get if you are running a Crystal Report or Spreadsheet update and use SQL authentication.

SQLLastDataSource=Data_source_name

The name of the data source the current computer was most recently connected to. This setting is automatically created and updated every time a different data source is accessed. This is the behavior you see in Dynamics GP. You cannot force the Data Source in Dynamics unless you manage your .ini settings using the Support Debugging Tool. For GP 2013 there is a new dex.ini switch that prevents the user from selecting another data source. This new switch is covered below:

EnableServerDropDown=FALSE

When set to false, this switch will disable the Server drop down field on the GP login window. In this case the Server field will default to the ODBC data source specified in the installation folder's dex.ini and can't be changed. This would typically be used if you have multiple data sources on the computer and don't want the user to use any of the other data sources.

SQLLastUser=User_ID

The user ID of the most recent user to connect to a data source using the current computer. This setting is updated every time a different user connects to a data source using the current computer. You cannot force the User_ID displayed unless you manage the Dex.ini settings with the Support Debugging Tool.

Kind regards,

Leslie
soma 24,410 on at

Like (0)

Report

RE: Dex.ini settings

Just try to add only below elements to Dex.ini file.

SQLLastDataSource=GP2013 R2

SQLLastUser=sa

Hope this helps!!!