|
I had another thought which might be helpful to folks in this kind of scenario. Consider creating, perhaps via DFU, a "conversion file" which contains the old class code & the new class code, assuming there is a one-to-one correspondence, which will not always be the case. There would have to be a field with a flag meaning - use the one-to-one - vs. use rule # whatever, whose annotated code might be in another file or source code member, indexed by the rule. http://www.outlookcomputing.com outlook@outlookcomputing.com (Mitch Cohen of File Track) This product is a great tool that we have used in the game of jigsaw puzzle when re-designing an application - move these fields from those files, expand this date format, total that, change this, but in your case it can be used to enforce standard consistent transcription of codes, with all programs for all files doing the same substitution algorithm, with automatic generation of a good chunk of what you need. Using file track, you could say for file-whatever go through the class-code field of all records & look it up in the DFU-conversion file & if the rule is one-to-one then make the substitution, otherwise import the code for whatever rule applies & execute it --- this way the same rule is followed every time you hit the same condition, regardless of file, assuming you catch them all & carefully write the code for your rules. Al Macintyre +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
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.