|
Another suggestion, depending how robust you want to make it, would be to setup a file of "tokens". That being words or abbreviations that are followed by an invoice number. And also a file of separator tokens (ie space, comma, semi-colon, etc). Then your program could read through each "token" doing %SCAN's to find if the token is in the description field. Just another approach. The only reason that you might want to do this is to save a program change if you find a new spelling, or a new way that the invoice is identified in the comment field. Jeff Stevens Mize, Houser & Co. P.A. 913 451 1882 JStevens@xxxxxxxxxxxxxx steema@xxxxxxxxxxxxx Sent by: rpg400-l-bounces@xxxxxxxxxxxx 01/27/2006 01:00 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc Subject having to find an inv. # in a comment field :( Well this is the picture. Don't ask why, but we get some info from abroad. They put invoice numbers in a comment field. The comment field can have normal comment info (not invoice number) but when there is the invoice there, I need to put this in some other work file. The len. of this comment field is 40. It is not uniform. The ways it is there are: INVOICE# XKC03J143L INVOICE # XTG05K023L INVOICE # XSC06A016L INV# XKC03G091L INV. XTC05L053L INV 5400960 INVOICES XTC05F008L AND XTC05F012L (in this case, I want to write 2 records) INVOICE XTC05F009L INVOICE #'S 2107071, 2107073 & 2107079 INVOICE #'S XSC04H008L & XTC04H021L IN addition, there are several spelling mistakes on the word Invoice, but these are not my concern ( I was thinking how to take the file, run it in Microsoft spell check, perhaps someone has done this?). Any thoughts on the coding would be appreciated. Thanks, Steve INVOICES SHIPPED AFTER COST CHANGE (an example of a real comment)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.