Observations on Grids / Format / Tabs

Since going live about 18 months ago, we have had an unusual number of problems with tabs. We have been able to work around a large number of these problems. We know that there have been a large number of issues depending upon the following factors:

1. Pre SP16 vs. Post SP16
2. Version of Internet Explorer
3. Win98 vs. NT or Win2K
4. Overrides for *PUBLIC vs. Group vs. User
5. Customized Apps vs. Vanilla Apps

One of our users that has made the following observations with regard to customized apps:

Observation #1:
1. If you need to create a new tab/grid, add 1 new tab and exit the application.
2. Go back into the application and create a second tab that you want to customize. Customize the 2nd tab and log out of OneWorld.
3. Leave the 1st tab "pristine" avoids future grid issues.

Observation #2
1. If you have a pencil symbol on a tab, there is a grid sequencing problem.
2. Access the grid sequencing screen for this tab. Verify that the grid sequence is set up properly.
3. Save the tab. Exit the application. Re-enter the application. The pencil symbol is removed from the grid.


CAN ANYONE CORROBORATE THESE 2 "OBSERVATIONS"?

Our experience is in exact agreement with your first observation.

No info on second observation.

Dave Mallory Xe SP 17.1 Oracle 8.1722 NT 4.0

pre SP16, the following process works well for us in creating new formats for an application:

1. If no prior "Default JDE" format exists, create one by clicking on the "New" button and change the name to "JDE".
2. Modify the format by dragging columns around, etc until its what you want, then click "new" again. Rename the new format to the desired name.
3. You may do this a few more times with the same or other apps before LOGGING OUT of OneWorld. The changes do not actually get saved permanently until you do this but is kept in a cache of some kind so don't wait too long to log out.

here's a clip on Pre and Post SP16 format handling from document ott-02-0028:
-------------------------------------------------------------------
Changes to User Overrides with Service Pack 16
Prior to SP 16
The first time that a user brings up a OneWorld application form, the system reads the User Override table (F98950) and creates a disk cache on the workstation. This table contains form-specific information such as menus, buttons, and formats. This cache serves to improve OneWorld network performance because multiple database fetches are not required to retrieve the individual form elements. However, if a system administrator or the user modifies user overrides using the User Overrides application (P98950), the override information is written directly to the F98950 table, and not to the cached table. Because OneWorld® always reads overrides from the cached information, any modified user overrides cannot become effective until the user exits and reenters OneWorld, causing the cached table to be refreshed. Also when users create new overrides within an application, such as grid formats, this user override information is held in cache until the user successfully exits OneWorld. Once the user signs out of OneWorld, the user override information is then written to the User Override table - F98950.


After SP 16
The way user overrides are handled within OneWorld® was rewritten beginning with SP16. The user overrides were changed from a binary format to an XML format, which allows for better management of the overrides. One major change in functionality is that now a user does not have to log entirely off of OneWorld® for the overrides to be saved, instead the overrides are saved when the user exits the application.

Due to the rewrite of User Overrides, there have been some complications with pre-existing grid formats created prior to this service pack level. If encountering problems with these pre-existing user overrides, you may want to delete and recreate them so they will be created in the new XML format for User Overrides.

Another important aspect of the change to user overrides, is that you must be on Internet Explorer 5.5 with SP2 applied along with mdac 2.6. This is necessary due to an updated/commonly shared Microsoft dll that OneWorld® utilizes.

Occasionally, there are issues with specific applications that the design of the application causes issues with the rewritten user overrides. Currently, the workaround when this problem is encountered is to get the latest ESU available for the object.