re:output section
Posted in 1994
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL
}>From: london@drawbax.attmail.com }>Date: 24 Jan 94 21:38:21 GMT }>To: informix-list@rmy.emory.edu }>Message-Service: mail }>Subject: output section }> }>Fellow sqler's and 4gler's, }> }>If this is a trivial question forgive me but.... }> }>Is there a way to "variablize" the report to statement so a user can input }>the destination, in either 4gl or ace reports. So far the only solution I }>was given was to have separate reports for separate destinations all }>hardcoded in the reports. This makes for many of the same reports all }>going to different printers or files. I'd like to cut down on duplicate }>reports. I have many. }> }>Thanks in advance }> }>Brian London }> }>J.M. Rodgers Co., Inc. }>245 Woodport Road }>Sparta, NJ 07871 }>(201) 729-6700 /* "You got the right key baby but the wrong }>attmail!drawbax!london /* keyhole", Steven Tyler, Aerosmith }> Brian, When I have a situation like this, using simply ace, I use the following: in my ace report I use report to pipe "cat > $HOME/report.rpt" to generate the report. I use a UNIX shell script to run the report and either prompt for the printer destination and store it into a shell VARIABLE or use a case statement to prompt for the destination selection. At any rate, I use shell to cat $HOME/report.rpt | $DESTINATION. Therefore you need only one ace report that can be set to any destination. Rhonda Hackenburg rhackenb@letterkenn-emh1.army.mil