Subject: | |
From: | |
Reply To: | F. Alfredo Rego |
Date: | Wed, 28 Feb 1996 11:44:54 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
<Elbert E Silbaugh> <[log in to unmask]> wrote:
>Steve Patrick wrote:
>
>.... big snip ...
>
>>be sure your MaxCapacity, Initial capacity, and incremental amount
>>are all multiples of each other.
>
>Since I just got done doing some DDXing, this prompted me to
>verify the numbers I went thru the other day...
>
>Few (if any) of mine are that way. And I decided it was OK that they
>aren't because either the final expansion does not necessarily
>have to be the same size as all the previous ones; and/or
>
>The final block of a detail does not have to be full. Therefore,
>evenly divisible increments (as alluded to) may not always occur.
>
>Or else my DB is all screwed up.
>
>Elbert
Fortunately for you (and countless others), Adager has ALWAYS enforced
multiples-of-the-blocking-factor values for InitialCapacity,
MaximumCapacity, and Increment. This applies whenever you enable a detail
dataset for DDX with Adager and whenever you specify new values (via
Adager) for an already-enabled-for-DDX detail dataset.
To increase even more your defenses, as provided by the Adager fortress,
I'm just incorporating the final touches on a super-water-tight version of
Adager that, in addition to all of the above, checks for further
consistency in the "Increment" arena. Including, ironically, a relaxation
of an unnecessarily super-strict check on IncrementPercentage (which,
beginning in 1994, I was not allowing to be more than 100%).
Ah... good-old-DDX. It sounds simple but it requires a lot of work in the
background.
+---------------+
| |
| r | Alfredo [log in to unmask]
| e | http://www.adager.com
| g | F. Alfredo Rego Tel 208 726-9100
| a | Manager, Theoretical Group Fax 208 726-2822
| d | Adager Corporation
| A | Sun Valley, Idaho 83353-3000 U.S.A.
| |
+---------------+
|
|
|