having been through a few bpcs data conversion efforts, i'm pretty sure a 
simple CPYF won't work. you may well run into fields, such as status code 
fields, with the same name that change from numeric to alpha of vice versa. or 
they change from a value of 0 or 1 to Y or N.

i believe that bpcs has conversion programs to go from 4.05CD to version 6. you 
might use those. or we have used a product called Intelligent Data Conversion 
System (IDCS). it is very inexpensive and it generates RPG conversion programs 
that convert from one file to another. you map the input field to the output 
field and it generates the code for you. of course, if you are changing the 
format of the fields, you have a little more work to do. if you know what you 
want to do, AS/400 query or SQL might also do the job.

chick doe
barton instrument systems



>>> Amitava.Banerjee@trin.net 02/27/02 01:02PM >>>
Hi
I am trying to copy the AVM file in 4.05 CD to AVM in 6.0.04. Now the 6.0.04 
version has more fields than the other one. Beside that,  there are some fields 
that have same name in both files but with different attribute. I tried CPYF 
with *MAP *DROP, but it did not work (*DROP does not work if different 
attribute exists). *NOCHK did not work too. Any other idea?
TIA
Amitava


_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.




This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].