Denis,
Probably I can't understand your problem.
I'm not also speaking English as native language and our alphabet too has weird characters where no other country uses (ie: İ,ı,Ğ,ğ,ş,Ş - not sure even if you'd see what I typed right:).
For those characters asc() codes are not same for windows ANSI and DOS codepages. IOW if a table is edited under DOS Turkish normally I wouldn't see it right in Windows unless a translation is done. Thanks to Foxpro all I need is to set table's codepage to origin 857 for once. From then on both windows and DOS could edit it and they both see it right. To prevent a translation if I ever need it I simply set its codepage to 0.
Both windows 1254, DOS 857 (Turkish) codepage marked tables display right in .Net for me.

Password, encrypted fields and alike are special in that you should prevent translation in the first place (char (binary), memo and memo (binary) map to DBTYPE_BYTES which is what you need). It works with VFP to .Net, .Net to VFP, VFP to SQL server, SQL server to VFP ...
IOW I'm saying to touch only to those fields which strictly need no translation between systems.

Cetin

>Cetin,
>Thanks for reply..
>About Thread.. I don't know how it can help me..
>About char/memo binary.. right.. ok.. but it realy not easy to update ;) but... what if we will use russian character set and 1251 codepage? I need for all strings change tables to char(binary)? It seems there must be way to prevent translation... it seems not all peoples of the world speeking and writing english ;)) yet....
>
>>>Hello,
>>>I have next problem
>>>My VFP table has 1252 codepage.. When I using .NET and DataAdapter.Fill() I preview my data in DataGrid. The codepage is not same.
>>>Problem - I using CIPHER encrypted columns. and encrypt wrong from .NET because strings is not correct.. Some is ok.. but some string ASC() for characters wrong..
>>>
>>>
>>>Question. How do I get same codepage in .NET datatable?
>>>
>>>Thanks
>>>Denis.
>>
>>Denis,
>>Thread #1043844 might help.
>>However for things like an encrypted password, GUID and alike use char (binary) or memo (binary) datatypes in VFP tables to prevent any codepage translation.
>>PS: Check for a message titled something like "valid GUID" earlier today in VFP section for a sample.
>>Cetin