GUB: Give me all your money... I've got a GUB!

[John Esak]

Well, this isn't an old Woody Allen movie... and it's not a BUG or a GUN...
so we'll use his choice. This is a GUB. :-)

Should you expect filePro to behave if you tell it to do something you
shouldn't tell it to do?  I dunno...

Put a subtotal field of say 3 or more characterless (even 1 will do, but the
effect is better with 3 or more... I've done fields up to 50!) on one of
your reports. Somewhere in the subtotal area put the system maintained field
for subtotal field value... @sf.  In other words put *@sf somewhere in this
area.

Run the report with:

dreport filename -f output -a -u

Works great, tastes light.  No problem.

Now, juke filePro by telling it to run in two directions at once by adding
an index sort to your output like this:

dreport filename -f output -iA -u

Take a look at the @sf values now... mysterious, huh??  I wouldn't say it's
a BUG, but it's certainly a GUB!

John

Normally, using the filePro interface you would only get either/or on the
index sort or sort/subtotal page... never both. By adding this to the
command line... without a -v table to help things out... this tiny
oddity/blow-up happens.

For those who don't want to try it... the first character of the @sf is
displayed properly, after that every character for the field length is a
high order number like \305 \304, etc. Lots of picture frames or octal
numbers appearing on your report.