New Era 2.20 - problem with state management in AFCL
Posted in 1998
Imagine a Master-Detail supertable with several tabs, two freeform devoted to the Master supertable and the remainder devoted to a series of gridform Detail supertables. The Master supertable is a loan and the Detail supertables are lists of borrowers, guarantors, securities, etc. The gridInsert button explodes to a freeform screen allowing a new role record (e.g. person or corporation as borrower or guarantor) to be entered. On the freeform screen is a button initiating a zoom to another gridform table from which an existing record may be selected if desired. After the zoom, the freeform screen is populated with the selected record and pressing the Accept button returns the record to the original gridform detail table. That is what is supposed to happen and so it does - sometimes ! On other occasions, the freeform table is populated, but the Accept button does not become active until focus is passed to one of the fields. Then, a staledata event is registered, making it difficult to get control of the data. The zoom gridform table returns the primary key. The freeform table loads the entire record and the data for the original gridform table is returned in seed Superfields - all as described in the AFCL documentation. Obviously, this is all to do with the state management system inherited by the MastDetlsupertable. My problem is - why should this happen in some cases but not in others. Are there any state changes triggered of by particular mixes of superfield attributes that are not mentioned in the documentation ?. We have been scratching our heads for weeks over this one and will be pathetically grateful for any advice leading to a resolution !!