Import ASCII file

[Richard Kreiss]

Can use the same method to get date and then construct a browse lookup to
put the "report" on screen.

I did this some years ago for a client.  Six different options presented on
a menu.  Each menu option had its own screen for inputting data into dummy
fields.  The browse format was based on the option selected and drop was
used to filter the data.  

They could look at open order information, work in process, shipped orders
and invoices.  The browse allowed for scrolling through the records.
Depending on the option selected, selecting a record would close the
original browse and open another based in what was selected.  i.e., select
an invoice and get the invoice details.

This was about 10 years ago.  This option would actually work much faster on
today's computers.




> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Scott Nelson
> Sent: Friday, April 15, 2011 11:40 AM
> To: filepro-list at lists.celestial.com
> Subject: Re: Import ASCII file
> 
> 
> > Note that I "discovered" a method some years ago, where you don't need
> > a record to sit on.  Run the import in *clerk, and put the processing
> > in the @MENU handler.
> >
> 
> And this groovy method is also a great way to do reports from large files.
> Build the input process to ask the user questions, look into the files for
the
> report data by the indexes, put the data into variables, use the formm
> command and you have a fast and flexible report.
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list