browse lookup in report

[Scott Walker]

-----Original Message-----
From:
filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.com
[mailto:filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.
com] On Behalf Of John Esak
Sent: Friday, December 11, 2009 5:09 PM
To: 'Enrique Arredondo'; filepro-list at lists.celestial.com
Cc: filepro-list at lists.celestial.com
Subject: RE: browse lookup in report

		 

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Enrique Arredondo
> Sent: Friday, December 11, 2009 2:32 PM
> To: filepro-list at lists.celestial.com
> Subject: browse lookup in report
> 
> Why can't we use browse lookups at the selection processing 
> of a report ?
> 
> Is there a scientific explanation for that?
> 
> thanks
> 
> EA

Yes, the answer is. Just because. 

Now this worked when my sister used it on me back in the 50'.  Has it lost
its power?

John Esak

P.S. There really is probably no technical reason why the browse function
couldn't be adapted to work without the concept of a screen behind it.  The
larger issue is that a browse by its nature is a mechanism that allows the
user to select one (1) record. You would have to arrange some "other"
processing simply to hold any records (more than one) on which you were
going to run the report part of the whole routine.  There are numerous ways
of doing this of course... None really perfectly suited, but some ideas do
come to mind as work-arounds.  Sit in rclerk and run your browse against the
file from which you want to select records.  Store them in another file
congruent to the first file and then ump out with a SYSTEM command to
actually run the report on that spin-off file.

Another really off-the-top with no sanity checking at all that would run in
select processing is:

Put up an array (you know a listbx) of the file you are sitting in.
Selecting a choice from the listbox would lookup dash you to that record and
select it, then put up the array again.  When they were done picking
records, lookup dash to the last record in the file (based on the command
line choice of an index) and END.  The report would then run with all the
choices made through the listbox method.  Very strange, but I don't see why
it wouldn't work.

John



I often have wanted to be able to use a browse lookup in sort/select
processing.  Think about it...you are running an Accounts Receivable
report...it asks you "All Customers or Single Customer".  You say Single.
Then it says "Enter Customer Code to Select: ".  OK, since you want the
report for "Republic Viking Engineering Design Services" you now have to
magically remember what their customer code is.  It would be great to enter
the first few characters of their name and then press <F6> to pop up a
browse lookup of the customer file.  Make your pick and away you go!  That
feature alone would have made me move to 5.6 since most of my reports have a
lot of selectivity where you need to use the appropriate code (ie.  Customer
Code,  Factory Code,  Salesman Code,  Office Code,  Category Code, Part#,
etc.)


Regards,

Scott


Scott Walker
RAM Systems Corp