2014.10.14 MSS Code Factory 1.11.12458 Service Pack 3

Service Pack 3 deals with refreshing the data as cached by the Obj layer
of the manufactured code.  All of the Obj.getRelation(), Obj.read(), and
TableObj.read() methods have been overloaded with a new signature taking
a "forceRead" boolean parameter.  If this parameter is true, the cached
information is refreshed from the database backing store.  If false, the
data is only read from the backing store if it's not already in the cache.

The original methods that did not have this extra argument have been modified
to simply call the new variations with a forceRead value of false.

The Swing prototype GUI has been updated so that reads are forced when you
open a Finder window or a ViewEdit window, including all component objects
displayed by the element tab of the ViewEdit.  In the unlikely event that an
object is deleted by another user, the ViewEdit window will come up with blank
fields.  In that case, you should close the ViewEdit, the window that was used to
bring it up, and re-open the window that was used to launch the ViewEdit.  The parent
of the ViewEdit will refresh itself from the database when launched, and you'll no
longer have visible references to the stale data, although the instance will probably
still exist in the cache.

Stale cache data can also occur when deleting complex objects, because the hierarchy
chasing is done entirely at the database end, so the subobjects aren't forgotten
by the client-side cache when the main container object is deleted, although the
reference to the container itself will be forgotten after the delete.  However,
with the forced read of sub-elements when displaying other objects that used to
refer to the stale data, those objects are refreshed and the stale references are
not used.  So while this results in some memory leakage, the user interface should
behave properly.