|
Field Usage Summary |
  
|
|
Field Usage Summary |
|
When the folder is selected the <Field Info> button becomes active. Clicking the button will display the Message Class summary information window for the currently selected Message Class.
Field Information Summary Screen
| 1. | Clicking on any of the column <Headers> will re-sequence the list accordingly toggling between ascending and descending modes |
| 2. | Clicking on the Field Display Option button displays the various modes available for displaying fields |
| 3. | <Save Summary> will save the field summary list to a CSV (comma separated values) text file |
| 4. | Shows the number of <Field Errors> found in the contact folder (see below) |
Field Errors
In the vast majority of cases, <#Fld Errors> will reflect a value of Zero. However, in some circumstances, one more fields will be reported as having an error - most commonly being <Err: 0x80040403 - MAPI_E_TABLE_TOO_BIG in technical terms)
Any field being reported with this error does NOT impact your data and it is not something that has any impact in your day-to-day operation of Outlook (leastwise not in any way that can determined). This error does not in any way hamper CG Toolkit's ability to use or update the field. It does impact the speed in which the contact folder can be processed if any fields used within a given ToolKit function have this error.
Based on tests using both internally created samples as well as a very extensive library of custom forms sent to us from customers over the years, the two most common themes as to cause seem to fall into one or both of these categories:
| 1. | The custom form has been extensively and repeatedly modified. These kinds of forms are more prone to underlying errors |
| 2. | The PST file in use is one that has gone through several upgrades from prior versions of Outlook |
To stress, the above two items are speculative since nothing has been found that allows this issue to be replicated on demand so it is impossible to determine the exact cause with 100% certainty.
The following can also be stated about error <0x80040403>:
| 1. | Once a field is reported as having a MAPIErr - it is permanent. This is not a situation of it having an error in one session of CG Toolkit and not in another. |
| 2. | This error can affect both standard and user-defined fields with or without a custom form |
| 3. | Publishing the same form (under a different name) to another folder, either in the same PST file or a different PST file, will generally result in different fields having an error or NO fields encountering the error |
| 4. | The error is "data independent". Ergo, you can perform step #3 using either the identical data or completely different data - there will be no difference in the results. Tests have been run using a custom form that exhibits the <Field Err> problem with different folders, different PST files, same and different PST formats, same and different data, and every other combination imaginable - all with different results in terms of what (if any) fields are reported as having a <Fld Error> |
| 5. | Simply <copying> a folder in its entirely will generally result in different fields (or no fields) being reported as having a MAPIErr reported |
| 6. | Running ScanPST on the PST file makes absolutely no difference |
| 7. | This error can occur on both PST and Exchange based folders |
| 8. | This error is not Outlook version specific (Outlook '2000-'2007) |
Field Errors and Performance
CG ToolKit uses different methods for accessing Outlook data depending on whether or not the fields required report a MAPIErr (fields being used for filtering data or as part of the selected function). The worst case scenario is that very large folders would be processed considerably slower then would otherwise be normal especially if it involves an Exchange based folder on a slow (or less than optimally configured) Exchange server or network connection. The speed in which a single contact item is accessed from an Exchange server is not representative of how fast the response will be for hundreds or thousands of contact items across a network connection.