>>>>Why does C# char = (char)134 return different value character than VFP char(134)?
>>>>
>>>>UPDATE. I understand why but have not found the way to resolve my issue. I need to get a character (in .NET program) (for number 134 or higher) that match exactly the character that VFP gets when using char(134) and such.
>>>>Any suggestion, please let me know. Except I cannot change the VFP code.
>>>
>>>
>>>Since .net uses UTF-16 to store a char ( one char = 2 bytes ), you do not encode chars
>>>
>>>When chars are stored to a file, they are first converted to a sequence of bytes (1, 2, 3 or 4 depending on the char and the encoding utf8, utf16, single byte char set, double byte chars set) and the byte sequence is written to the file
>>>This means that a file does not contain chars, but bytes
>>>
>>>You convert the chars to a byte array first, using an encoding, then encode the byte array
>>>
>>>Supposing your code page in vfp is 1252
>>>
>>>

>>>		internal static void Go()
>>>		{
>>>			// from byte to string
>>>			byte[] src = new byte[] { 134 };
>>>			string p = Encoding.GetEncoding(1252).GetString(src);
>>>
>>>			// from string to bytes
>>>			string s = "†"; // chr(134) in 1252 codepage
>>>
>>>			byte[] bytes = Encoding.GetEncoding(1252).GetBytes(s);
>>>			
>>>		}
>>>

>>
>>I re-read your code example and I see the solution there for me. Thank you!
>
>Good because I did not understand your first reply

To clarify: in .NET when my code converts space (char(32) to an 'encrypted character' the logic is:
1. Get the ASCII number of this character (empty space). Which I can do as you suggested:

    byte[] bytes = Encoding.GetEncoding(1252).GetBytes(" ");

2. Add 102 to the resulting number (in step 1)
so I have to add 102 to the 'bytes' and create new byte[] named NewBytes.
3. Get the character corresponding to the new byte:

    string Encrypted = Encoding.GetEncoding(1252).GetString(NewBytes);

The step two is what I am still not clear how to do.