System command, dreport and data transfer

[Fairlight]

Confusious (Dan Snyder) say:
> I chose the approach I described for the following reasons.

All valid reasons, and you don't have to justify your code choices to me.
You asked for suggestions, I gave mine.  As I said, one approach.

> So you're saying that my approach should work when called from "D-Request
> Output"?  That way I can use it on a group of records simply by selecting
> those records like I was running a report (rather than writing code to
> select and loop through records)?  My code works fine if I manually enter
> data from one record on the command line simulating the "system" call or if
> I attach the code to a key in the input processing table.  My code just
> doesn't work when I try to call if from @wbrk1 when subtotaling on a part
> using "D-Request Output" which is "dreport" I think.  I was asking to if a
> "SYSTEM" call to "dreport" should work from "dreport".

Yes, using SYSTEM() to call dreport should work from dreport.  If it's not
working from @wbrk1, either that event is never hit, or there -may- be a
bug or perhaps a "known limitation" that prevents it from working in that
specific case.  Maybe Ken can confirm or deny.  Posting the relevant code
segment may help someone see why it's not working.

People have called *report from *clerk and *report for years, myself
included.  It's not supposed to be an issue--unless you're out of license
seats.

Yes, Request Output is dreport, assuming you didn't alter your menus.  We
say *report or *clerk to accomodate both the "d" and "r" versions, which
stand for development and runtime, respectively.

mark->
-- 
Try our new SPF-0 lotion, SunScream[tm].  Get it while it's hot!