Issues Resolved in Dexterity/Runtime 8.0 Releases

 

Posted: August 31, 2007

This page contains the list of issues that have been resolved in the 8.0 releases of Dexterity and the Dexterity Runtime Engine. The Dexterity 8.0 Runtime Engine is the one used in all client installations of Great Plains 8.0.  The issues are listed below with the appropriate release in which they were fixed. The most recent release of Dexterity and the Dexterity Runtime will include all of the fixes listed for that particular release, as well as the fixes added in the previous releases.

Dexterity/Runtime 8.00m88 Fixes

Dexterity – Bug #39180 – TextFile_Open() function is not returning a valid file handle
Resolved: Dexterity was not handling the return file handle from Windows correctly in rare cases.  This caused text files written by Dexterity to be created but not written or closed until Dynamics was exited.

Dexterity – Bug # 40377– Landscape Cannot print more then 32767 pages to the printer - (Page start range can't be > 32767)
Resolved: This has been corrected.

Dexterity – Bug #40379 - COM automation crashes after automating several times
Resolved:  When using COM automation on potentially any application, Dexterity would fail with an automation error in some cases.  This has been corrected.

Dexterity – Bug #40380 On Dynamics 8.0, using the scrolling wheel can cause the system to lock up for 2 to 4 minutes.
Resolved: This has been corrected.

Dexterity – Bug # 40381– Runtime crash when script logging a custom application
Resolved: When using the Script Debugger to debug an issue in runtime, sometimes Dynamics would crash with an Exception error.  This has been corrected.

Dexterity – Bug #40398 - Some special characters may cause Dynamics to crash printing a report.
Resolved:  Commonly this would happen if the graves symbol (the backtick ` not to be confused with single quote ‘) was in certain control fields and certain reports were printed.  RW was changed to allow printing of this and other special characters.

Dexterity – Bug #40416 - FP Null field address message inside try/catch statement
Resolved: Using exception handling in try/catch statements in Dexterity should catch exceptions when fields are referenced incorrectly.  In some situations, this was not happening and FP Null field address errors would occur.  This has been corrected.

 

Dexterity/Runtime 8.00m86 Fixes

Dexterity – Bug #23041 – Runtime error when programmatically filling in data with VBA code
Resolved: Previously it was possible to “overflow” a string field in Great Plains with VBA causing a Dexterity Runtime error.  This has been corrected.

Dexterity – Bug # 24971– Landscape Adobe Printer Settings Not Recognized In Application.
Resolved: A previous service pack bug fix caused the Adobe Print to PDF not to print out in landscape mode.  This has been corrected.

Dexterity – Bug #25460 - Utility_EncryptTableString Dex function does not match GPConn TableColumnEncrypt function
Resolved:  The 2 methods called now both encrypt the same string correctly.

Dexterity/Runtime 8.00m85 Fixes

Dexterity – Bug #19934 – Client Slowdown when posting thousands of batches from Series Posting
Resolved.  The algorithm for inserting records into the background queue wasn’t optimal and the time to insert the batches into the queue was taking exponentially longer per record added.

Dexterity – Bug #20384 – When using GroupWise 6.5 to email Collection Management Letters the carriage returns are ignored.
Resolved:  This was determined to be a GroupWise problem but a workaround was implemented to make the emails show correctly.

Dexterity – Bug #14234 - You receive the error "When you create a PostScript file you have to send the host fonts.  Please go to the printer properties, "Adobe PDF Settings" page and turn OFF the option "Do not send fonts to Distiller".
Resolved:  This error could occur because the default Adobe Printer settings weren’t being read by Dexterity.

Dexterity – Bug #16015 - DUOSObjectExtractID function returning incorrect values
Resolved: This VBA function was incorrectly parsing the passed in value therefore returning the incorrect values back to the programmer.

Dexterity/Runtime 8.00m79 Fixes
 

Dexterity – Bug #12793 - Microsoft Great Plains may crash or stop responding after the program has been running for approximately 50 days
Due to the use of an obsolete windows system call, if Great Plains has been open approximately 50 days without being restarted, Great Plains may crash.

Dexterity – Bug #10120 - Max symbol length exceeded: increase MAX_TOK_LEN Error on modified reports
Due to an internal problem with report writer, modifying a "complex" report such as the POP Purchase Order Blank Form would often give this error when running the report.  The internal bug has been resolved.

Dexterity – Bug #13080 - You receive the error "Dexterity Development Tool has encountered a problem and needs to close." when building a reference table on a Great Plains SP2 dictionary.
When creating the script reference in Dexterity, Dexterity would often crash making the reference file.  This has been resolved.

Dexterity – Bug #13233 - VBA modifications sometimes fail to import
The fix for Bug #9849 didn't fully resolve the VBA Package file import problem.  After making a correction in the core package import code, the problem package file could be imported successfully.

Dexterity – Bug #11269- Data sometimes not returned from COM method call in Dexterity
Due to a problem in Dexterity with passing long integers to a COM method, Dexterity was sometimes sending/retrieving the wrong value making the function not work correctly.  This has been resolved.

Dexterity – Bug #9392- Memory problems with Listview controls with a lot of rows/data under Win2000 Pro
With the common use of memory tables with Smartlist and other applications, memory becomes fragmented and not useable with memory based tables in Dexterity.  Because of this, very often errors would happen on random memory based tables.  To resolve this, all memory tables will now be created as ctree tables in the logged in users application data folder.  These files will be deleted when the memory table is closed and therefore work previous memory tables.

Dexterity – Bug #12949- Phantom prompts show in SOP Entry
This was an obscure problem that occurred in a specific situation where a field prompt would show in a spot where it should not have.  This was a redraw issue with the window and the issue has been resolved.

Dexterity – Bug #12513- Incorrect item is selected from a combo box
In some windows that used sorted combo box fields, particularly the Job Link Advanced Search window, selecting a value from the drop list would then actually select a different field instead of the real value selected.  This has been resolved.

Dexterity – Bug #15516- ScriptLog_Start() function does not create log file
With Dexterity 6.0, it has been possible to programmatically start the script logging capability in Dexterity.  With Dexterity 8.00m52, this has not been functional.  This issue has been fixed with 8.00m79.

Dexterity – Bug #15444- Dexterity gives error "Dexterity Development Tool has encountered an error and needs to close." when opening 3rd party dictionary that has globals with main dictionary datatypes
Dexterity crashes when opening 3rd party dictionary that has a global vairable with main dictionary datatypes.  Specifically this error happened with the POE2277.dic.  This has been resolved.

Dexterity/Runtime 8.00m76 Fixes
 

Dexterity – Bug #3068 - Must double click radio buttons and checkboxes to activate if focus on DDL
If the user is focused into a Drop List or Combo-box then clicks on a radio button or checkbox, 2 clicks were required.  This has be resolved to work correctly on 1 click.

Dexterity – Bug #8877 - Cannot call method in C# assembly that uses an array
Passing in an array to a C# .NET assembly would sometimes cause the system to crash or return incorrect results if it did not crash.  This has been corrected.

Dexterity – Bug #8915 - Context problem with commands
Dexterity – Bug #9740 - Advanced Lookup windows not displayed in Windows menu
Dexterity – Bug #9744 - Advanced Security menu items not displayed after changing registration keys
Dexterity – Bug #9839 - Command_GetTag() fails for main dictionary commands
Dexterity – Bug #10365 - Purchasing Receipt Numbers remains in Windows menu after window has been closed

These bugs were all the result of using sanScript to perform operations on Great Plains core dictionary commands.  However due to a dictionary context problem, this didn't work and the workaround was to use pass through sanScript to manipulate Great Plains core dictionary commands  This has been resolved.

Dexterity – Bug #9192 - Item Description Keyable Length
Changing the keyable length of a string field is allowable.  However in some circumstances this would unknowingly cause internal problems overwriting memory and causing system instability.  This has been resolved.

Dexterity – Bug #9357 - OLE Attachments on Notes stops functioning after GP 8.0 SP1 install.
A change in default options for the Visual Studio compiler changed the build behavior for the contain.exe and caused it to fail.  The switch has been manually selected and the contain.exe built correctly again resolving the issue.

Dexterity – Bug #9379 - Illegal address for field 'Currently Stopped' when setting breakpoint in Startup script going into test mode
The changes using the Great Plains menu structure for 8.0 caused a problem when adding a breakpoint to any script in the Startup script or a script called by the Startup script.  This has been resolved.

Dexterity – Bug #9849 - Importing in Package files on Version 8.0 does not import the information correctly
Dexterity – Bug #10242 - Export of Package Files does not export the data correctly
Import & Exporting of Package files has not worked correctly in most instances in 8.0.  This problem has been resolved.

Dexterity – Bug #10281 - CurrentProduct not switching properly in 8.0 SP release
In Continuum using the Dynamics.Application object, with the 8.0m69 SP1 release, the .CurrentProduct method to switch the current product would fail.  This was a problem introduced with SP1 and has been corrected.

Dexterity – Bug #10573 - Dexterity Runtime Update breaks Terminal Server User Profile Launch
A change to the default Visual Studio compiler options marked the dynamics.exe runtime to be "Terminal Studio Aware".  This caused windows to treat the executable differently and perform different options when running.  The flag was manually changed to the "old" setting which resolves this issue during the new build process.

Dexterity/Runtime 8.00m69 Fixes
 

Dexterity – Bug #3049 Timed process appears to leak memory over time
A developer has encountered a situation where they are using a Process Server (dps.exe) to run some background processes with a timed event at a small interval. The symptoms of the problem is that the dps.exe would increase in memory size and over the course of a few days use up all the server memory. This has been corrected.

Dexterity – Bug #5456 Application exits sorting by Batch in Lookup
In the Advanced Lookup window for Payables Transactions, sorting by the Batch Number would most commonly cause Great Plains to crash. This has been resolved.

Dexterity – Bug #6641 Need to verify number of records when initializing a scrolling window
In some instances, when a scrolling window was filled Great Plains would crash. This was caused by a division by 0 error internally when calculating the number of records to make the proportional thumb support for the scrolling window. This has been resolved by trapping the division by 0 error.

Dexterity – Bug #7002 Create report that lists Window items that have changed resource ID's
Under Reports a new report called Resource ID Validation has been created.

The report will compare two dictionaries and show which forms, windows, and window items (strings, fields) changed resource ID's.

The old dictionary needs to be opened as the source, the new dictionary needs to be opened as the editable dictionary. When the report runs, it iterates through all of the forms, windows, and window items (strings, fields) in the source dictionary and tries to locate the resource in the editable dictionary by both its name and resource id.

- If the resource is not found by either its name or ID, the resource is reported as "may have been removed".
- If the resource is found by its ID, but not its name, the resource is reported as "may have been renamed". A more likely reason for this one, however, is that the original resource was removed, and a new resource took over its resource id.
- If the resource is found by name, but not ID, then the resource is reported as "RESID changed".

Dexterity – Bug #7369 Long dictionary paths crash when recording macro
When recording a macro and choosing a long path for the macro save directory or the path of any of the dictionaries to open, Dexterity Utilities would crash. This was caused by Dexterity Utilities only using 80 character strings for paths. This has been changed to 255 characters globally and the problem is resolved.

Dexterity – Bug #8510 Runtime_GetOSInfo() returns DEX_OS_WINDOWS_XP on Windows 2003
The Runtime_GetOSInfo() function returned the wrong value when used on a Windows 2003 machine. The function did not properly recognize the newest OS and reported it incorrectly. A new constant,DEX_OS_WINDOWS_SERVER_2003, has been added and the function will now recognize Windows 2003.

Dexterity – Bug #9357 OLE Attachments stop working after installing Great Plains 8.0 SP1
After installing 8.0 SP1, the OLE Notes were no longer working.  This has been corrected.

Dexterity/Runtime 8.00m52 Fixes
 

Dexterity – Quality/DE report #22039 -Add an "Are you sure?" dialog to Compile All button
In the Dexterity Resource Explorer, when the Compile All button is pressed a dialog is presented to confirm that the user wishes to run the potentially length compile operation.

Runtime– Quality/DE report #12622 -File Security does not work in Report Writer
In the Report Writer, file security isn't respected and data from tables will be displayed even if permissions to the user was removed from Great Plains security. This has been resolved.

Dexterity – Quality/DE report #21869 -Field_GetPosition() not returning correct coordinates
For fields that have been hidden using the hide command, subsequent calls to Field_GetPosition() on that field gave coordinates that were 10,000 too high. So if the field was at position 300,400 Field_GetPosition() would return 10300,10400.

Dexterity – Quality/DE report #22206 -delete line window Scroll_window blows up Dexterity
Using the delete line window XXXX or insert line window XXXX command and referencing a non-existent scrolling window would crash Dexterity when compiling the script. This has been fixed to return an error as expected and not crash Dexterity.
 

Top