Dynamics,Developer,Newsflash,G computer Dynamics GP Developer Newsflash: Great Plains Dex.Ini file s
----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc
As it historically was coded in Great Plains Dexterity, thisfile is Dex.ini. This file could befound in Dynamics GP workstation directory for versions 9.0, 8.0, 7.5, 7.0,6.0, 5.5, 4.0 and earlier, if you are on GP 10.0, then it should sit in Datasubdirectory. In this small publicationwe would like to come through some of its settings and flags:1. If you need to resynchronize Dynamics.dic fileto its account structures, especially if you believe that your Dynamics.dicfile was corrupt and you copied it one more time from GP CD #1. Change Synchronize to True and Initial toTrue. This will force Dynamics on thefirst user login to switch to Utilities and synchronize the dictionary, whichis your Dynamics.dic metadata and business logic file 2. Logging Dexterity, SQL and ODBC traces. This step is needed, when you sort of givingup in getting unknown error message in Great Plains. Assuming that you already did the researchtrying to find something about it in Microsoft Dynamics GP Customer Source. Even if you do not have support plan withMicrosoft, you still can get reasonable explanation on what is going on andprobably the idea on where the fix could be. Please make this changes in Dex.ini: SQLLogSQLStmt=TRUESQLLogODBCMessages=TRUESQLLogAllODBCMessages=TRUEThen find Dex.log file in the samedirectory, where Dex.ini is located. Werecommend you to make a copy of this file right after the moment when yourerror message triggers, and then review it with creativity of software programmer. More likely you will have the idea on whatwent wrong 3. GP Integration Manager Path. Here you typically have to fix this line: IMPath=. When you install IM, it tries to linkinstallation to your local Great Plains workstation, however, there are knownissues on Terminal Server/Ctrix and even fat GP clients. Please do not try to fix FRx client path inDex.ini. Instead, find FRXDYN.ini fileand change path there accordingly 4. Great Plains Dynamics legacy Dex.inisettings. Here you should know aboutlocation and locations translation theory in old Great Plains on Pervasive SQL(former Btrieve), or Ctree. The lines toreview are: Workstation=WINDOWS here WINDOWS with uppercases is the locationID to use for this specific GP workstation.
Dynamics,Developer,Newsflash,G