NewEra question regarding manualSF.setText() triggering lock under pessimistic locking
Posted in 1996
Topics: Performance & Tuning, Triggers, Constraints & Referential Integrity, Clustering, Grid & MACH11
We have many instances in our applications where we want to do setText()'s on manual superfields without triggering a lock event on a supertable that has lockmode as pessimistic locking. We had a workaround for this in versions prior to Newera 2.2, but 2.2 has seemed to change something that has broken our workaround. Does anyone out there have similar needs? Have you been able to successfully address these needs? Any suggestions, or comments would be appreciated. Thanks Options we have already tried and rejected: ixTextBox : Do not have many of the same general characteristics of sf's. Can only carry one row of data Addtional noLock SuperTables : Unwanted added overhead. Manual SF's not desiring lock must be visually grouped together. Neither of these above options work for grid form ST's set manual sf in retrieve during rowRetrieved event : Not always possible from a business app standpoint. Not always performance viable. Does not allow refresh of non dbs calculated fields without doing a st.retrieve on the entire dataset