Download Release Notes - Logistic Engineering Services

Application: eMRD 5692
Issue No: 446
Date: 09-Feb-15
SQL TEST - Error box has incorrect commentry!
Corrected SQL statement which caused this error when working with an SQL Server database.
Issue No: 448
Servicing/Task error on Task Summary report
Query modified in Task Summary report to correctly relate tasks on LCNs with servicings.
Issue No: 449
Problem saving data from the Item Identification form
Item Identification form redesigned. See Issue 444.
Issue No: 452
SQL TEST - RunTime error when adding PN to ACRN set.
See Issue 456.
Issue No: 453
SQL TEST - Part Number Library deletion process!
The deletion of Part Numbers / Cage codes has been modified.
The check which determines whether part numbers are in use now displays and optionally prints where the part number /
cage is used.
The Part Number / Cage can now only be deleted once all the links have been deleted.
Issue No: 454
SQL TEST - Cage Library deletion locks up EMRD.
The behaviour of the Delete Cage function has changed.
The list of PartNo/Cages to which the Cage is assigned can now be viewed and printed.
All PartNo/Cages to which the Cage is linked must first be deleted before the Cage can be deleted.
Issue No: 456
SQL TEST - Run-time error 35601 P/N Library try to add new line
This error occurred when performing an invalid sequence of steps.
When creating a new ACRN Set, the user must use an ACRN derived from the RefNo to which the LCN is linked.
If the user tried to create a new Refno at this stage, the error was raised.
Modified the code so that the user cannot create a RefNo and add it to the PartNo library when an ACRN Set is being
created.
Issue No: 464
SQL TEST - Issue XXX - Add FM
This is actually the error in Issue 443. Its just that the Item Ident form is launched when creating a Failure Mode if the
Minimum Equipment List field is not populated.
The fix was reported against Issue 443.
Issue No: 465
LCN renumber advises duplicate LCNs will be created
The Renumbering LCNs function has been enhanced to display the LCNs which will be duplicated.
Duplicated LCNs should only occur when renumbering a branch (as opposed to renumbering the whole structure) because
the new numbers which will be generated might be the same as a number elsewhere in the structure in an area that is not
being renumbered.
Issue No: 466
Populate LCN Nomenclature when adding a part
Code modified to assign the Item Name to the Nomenclature field when adding a Refernce Number if its not a Modified
Classical LCN and if the Nomenclature field is blank.
Issue No: 469
SQL TEST - Failure Cause unable to save
Corrected the SQL statement which was causing the error when working with SQL Server databases.
Issue No: 470
SQL TEST - Moving LCNs.
Corrected SQL satements which use the Asc function to work with both MSAccess databases and SQL Server databases.
Issue No: 473
Link the Root Cause form to the Failure Mode Details form
When entering a Failure Mode Cause, the user is now forced through the Root Cause process in an effort to have the
Failures Root Cause entered rather than a result of the Root Cause.
42
of
51