Dex in turn is written in C programming language, providingcertain level of computer platform independence in 1990th, wherethis question was actual for Great Plains Software position on the MRP softwareapplications market.  Dexterityarchitecture, especially considering current versions: 10.0, 9.0, 8.0 works onMicrosoft SQL Server platform through ODBC connection and in this smallpublication we would like to give you initial highlights on Great Plainstroubleshooting:

1.       "Good"and "Bad" Great Plains workstation.  Ifyou are experiencing error message in Great Plains, please try to calm down andanalyze - is it happening on all workstations or just on one of them?  If the answer is - only on singleworkstation, try to review its peculiarity. Log in GP, on the top-right corner click help icon and write down theVersion of Great Plains, something like 10.00.0903 (this is Great PlainsDynamics GP Service Pack 1 for example). Compare this number with Good workstation.  If the number is not the same - likely thatService Pack version is causing the problem. The simplest way to fix SP issue is either apply appropriate servicepack or copy GP folder from Good workstation to the one where you have theproblem

2.       Dex.Inifile.  This file has settings for yourGreat Plains user workstation Dexterity engine. Dexterity is obviously the player, where Dynamics GP faces all softwarerelated error messages at the first place: DLL, Windows and Great PlainsService Packs, SQL Native drivers, ODBC settings, corrupt REPORTS.DIC, DYNAMICS.DICand other Dexterity dictionaries to name few examples for you.  In order to understand the sequence ofevents, you should enable logging in Dexterity. Please change the following settings in Dex.ini file SQLLogSQLStmt=FALSEto TRUE, SQLLogODBCMessages=FALSE to TRUE and SQLLogAllODBCMessages=FALSE toTRUE.  If you do so, Dexterity willcreate DynSQL.log file (for version 10.0 in Data subfolder, in earlier versionsin GP folder)

3.       GreatPlains ReportWriter issues.  Corruptreports are common in the scenario when you are modifying reports in the sharedREPORTS.DIC file either by exporting and importing customization packages or bydoing direct changes in Dynamics GP Report Writer.  The fix is also very simple - either restoreREPORTS.DIC from backup or export reports in RW from "corrupt" REPORTS.DIC,then delete this dictionary and re-import reports

4.       GreatPlains Dexterity Customizations. If you already tried DexSQL.Log file methodand it didn't help your Dexterity programmers to fix the problem, consider thestep of installing Microsoft Dexterity on one of your computers and have yourDex developers to debug it

Source: Free Articles from ArticlesFactory.com