At 1:51 PM -0700 8/10/00, [log in to unmask] clarified:
>Actually, that wan't what I was thinking of...
...
>DDX enabled:
>DDX enabled as follows on new or existing sets.
>Capacity: 10000000,10000,1000
>Say you have a data set with 8500 entries and a limit of 10000.  You DDX it
>with max capacity 10,000,000 increment of 1000, keep initial capacity of
>10000.  You tell operations, "don't need to check this set no more, we're on
>cruise control".  1500 entries added to set, no problemo.  User on last day
>of month trying to ship end of month merchandise out tries to add entry
>10001.  Intelligent program doing mode 202 DBINFO complains.  Warehouse
>manager says, "What do you mean everybody logoff!".  You look for work at
>Dairy Queen.


Aha, thanks for clarifying. In that case, Lars' suggestion should work: Use
Query or some other tool to put dummy records in the set in order to cause
a dynamic expansion, then delete the dummy records once the expansion has
happened.

Note, however that this will only work for a detail with DDX enabled, but
not a master with MDX, since DBINFO 202 returns current capacity for
details, but only the primary (original) capacity for masters, even if an
expansion has occurred.

Obviously, the best solution is to fix the application to use DBINFO 205,
but unfortunately that's not possible for GP (or other canned application)
users. In that case, I'd say it's time to file an enhancement SR with the
vendor.


Barry Lake                              [log in to unmask]
Allegro Consultants, Inc.               www.allegro.bogus.com
(408)252-2330
--------
Attempting to use anti-spam technique.
Remove ".bogus" to create valid address.