Cached Override Information

The first time that a user opens an application form, the system reads the User Overrides Table (F98950) and creates a disk cache on the workstation. This table contains form-specific information such as menus, buttons, and formats. This cache improves network performance because multiple database fetches are not required to retrieve individual form elements.

However, if a system administrator or the user modifies user overrides with the User Overrides Revision application (P98950), the system writes the override information directly to the F98950 table, and not to the cached table. Because the system always reads overrides from the cached information, any modified user overrides cannot become effective until the user exits and reenters the system, causing the cached table to be refreshed.

For example, assume that you want to modify a journal entry by adding tabs and then associating those tabs with your user overrides. You would create the tab and then use the P98950 application to associate the tab with your user profile. You would not immediately see any records of the journal entry form because the user override is stored in the User Overrides Table, and the system is looking at the cached information. This process does not affect your ability to create and use local form changes, or workstation preferences, that are not stored in the User Overrides Table.

If for some reason you have two users who share the same user ID, be aware that the system does not share user override records. If both users sign on to the system at about the same time, the first of these two users to sign on will see the user overrides; the second user to sign on will not. Furthermore, the first user to make an override change during simultaneous sessions takes control of the F98950 record, and all other users signed on to the same user ID are locked out.