selection popup for output

[GCC Consulting]

From: filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com
[mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com]
On Behalf Of dave kasper
Sent: Friday, November 07, 2008 10:48 AM
To: filepro
Subject: selection popup for output

 


i am looking to do a report that pops up a popup selector table for the user
to choose wich record listed on the popup table to print. Can this be done
on output . i know it can be done on input but on output? dont want to use
selection set or ask to enter number (its long and mixed so hard to
remember) just want to give them the  list to choose the record to print.

 

any ideas?

 

thanks 

 

This can be done from output.  Use a list box to select the report and then
system out to run the repost selected.

 

However, it makes more sense to so the selecting from an input process and
then system out to run the desired report.  If parameters need to be passed
to the report, you can do this while standing on a record, get the
information and then pass it to a selection process.  Since this can be done
from an outside file, you are not locking the report file while getting the
parameters wanted.  This method also allows you to use browse lookups to
help the user if necessary.

 

I am currently using this method for a number of my clients.  In one case
they are given an option to either print a report of have Printwizard create
a PDF of the report using a listbox with the 2 options.  The process is run
from a library file.  If pdf is selected, the file name is set as an
environmental variable.  A batch file runs after the report to file is
completed using the variable set in processing.  If necessary I could also
use putenv and a listbox to select which printer to print the report to.

 

One thing, if you are a *nix system, both procedures will use up an
additional seat if your system is prior to 5.6.  With 5.6 a system call
doesn't use and additional seat. 

 

If you are running windows prior to 5.6, the system could not tell how many
users where on the system and therefore a system call didn't use any
additional licensed users.  It was up to the administrator or consultant to
insure that the user license was not exceeded.  With 5.6, see above.

 

 

Richard Kreiss
GCC Consulting

rkreiss at gccconsulting.net
  

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20081107/56689a43/attachment.html