Need to print a form from an import process using *report
GCC
gccconsulting at comcast.net
Mon Nov 28 15:09:26 PST 2005
> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf
> Of Don Coleman
> Sent: Monday, November 28, 2005 3:02 PM
> To: 'Fplist (E-mail)'
> Subject: RE: Need to print a form from an import process using *report
>
> John:
>
> I have an import process running from *report (fPv5.0.13RN9
> on Windows 2000 Advanced Server & WIN2000 & WIN_XP clients)
> which runs every 8 minutes. The app. creating the fP data
> file takes between 2-4 minutes and my import takes approx. 4
> minutes to complete. Throughout the day there are quite a
> few records that are changed due to a change in the
> customer's order, operator error etc. These orders
> (prescriptions actually) are then cataloged via a workflow
> application that I developed in fP and is ultimately sorted
> and packaged automatically via conveyor. I need the error
> log sheets to facilitate the "pulling" of orders that have
> been changed by the operator that have already been
> sorted/packaged. I will then direct these "error log" sheets
> to one of five laser printers situated around their sorter/conveyor.
>
> My original plan (not well-thought-out) was to add a form
> command to my import process and direct them to the
> appropriate printer around the sorter via the PFPOSTPRINT
> command & Bob Rasmussen's Print Wizard program (Strongly
> recommended!). It occurred to me after the fact that the
> form command is not available in *report. I created a new fP
> file that I post the appropriate data fields to, print the
> form from that file as part of the batch import process, and
> delete the entries that have already been printed.
> Of course, on the day I want to test it there are very few
> changes occurring. Two before lunch, none as of yet after lunch.
>
> It was either this method or do some type of ascii export and
> print function as described by several contributors. Any
> other suggestions are welcome.
>
> Don Coleman
Don,
You could move this process to *clerk as Ken suggested and then take advantage
of form, formmm to print the appreciate correction.
Using formm & form would allow you some flexibility in the output appearance.
Depending on your requirements, you could set up array(s) mapped to dummy fields
to hold the changed data and then print it out after completion of the import.
You could use a report to do the same thing but you would have to pass the
variables to the report using -r* values. Again this can be done using a system
call as previously suggested.
Richard Kreiss
GCC Consulting
More information about the Filepro-list
mailing list