Exactly, but I think we have it working by using cpconvert(1252,437,fieldname). We are testing it now. It seems that when retrieving data from a table with a codepage of 437, windows converts it to 1252 before displaying it, but when saving to a 437 table, it saves it in the 437 codepage. Correct me if I am wrong...
Tracy
>So your problem is years 1994-1999?
>
>>The year (4 digit) is uploaded to an AS400 system for auto policies. The original app is written in FPD26 and converts the year (i.e. 1985) to a two-digit code using the code below. Since the tables are accessed from both the original app and the new VFP app, the codepage is set to 437 on the tables. The problem is in the code below. It converts correctly until you read or write the conversion to the table and then Foxpro converts it again. I need a way to convert it where it can be read from fpd26 and vfp from tables with a codepage set to 437.
>>TIA
>>Tracy
>>
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
