 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Tue, 2 Apr 1996 09:18:26 -0500 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Check out my September 1994 Interact magazine on pages 38 (13)
MPE/iX DEBUG And DUMP Analysis.
I give debug examples for how to trace TurboImage calls dynamically!
More often than not this type of problem is the result of a sort item!
One real life example, a large HMO had a notes data set. For each member
inquiry call an entry was placed in a notes detail with a member number
path sorted by a four digit contact number.
All went well until the contact number reached 9999! Then the code moved
zeroes to the contact number and added the entry. How could the contact
number reach 9999? When someone called in that wasn't a member, an unknown
member number of all 9's was assigned. The entries built up over a period
of years.
The effects of adding the entry caused image to read up the 9999 entries in
the chain until the sort item matched, then using the balance of the entry
(the note text!) as the sub sort items it would eventually place the entry.
Since they were against deleting any entries, we simply assigned a new
unknown member number and the problem was solved, until they could remove
the sort item, which wasn't needed anyway.
**************************************************************************
********* __ __ * * *********
******** / / / / ** ** Michael C. Hornsby ********
******* / / / / *** *** President *******
****** / /___ ______ ____/ / **** **** Beechglen Development Inc. ******
***** / __ // __ // __ / ***** ***** 5576 Glenway Avenue *****
**** / /_/ // /_/ // /_/ / ****** ****** Cincinnati, Ohio 45238 ****
*** /_____//___ //_____/ ******* ******* ***
** __ / / ******** ******** Phone: (513) 922-0509 **
* / /_/ / ********* ********* Fax: (513) 347-2834 *
/_____/ ********** ********** Net: [log in to unmask]
**************************************************************************
|
|
|
