Thank you for that additional information.

>>Hello Dragan,
>>
>>I wanted to test it but I couldn't even just do a copy/paste of those characters ;-)
>
>That's because you're using VFP to access unicode strings, and it will conform to whichever codepage and locale are set on the current machine, while turning anything beyond that locale into question marks. Set the system locale for non-unicode apps on the box where you do this to whichever obscure language which uses accents when writing (!) (see the thread on accent vs diacritical on chatter) and then VFP should recognize them.
>
>You may also want to check various combinations of parameters in strconv() function - I know I sometimes get a string from SQL which I have to convert into something I can use:
>
>

		SQLExec(h, "exec sp_helpindex '"+tcTable+"' ", "crsTmpDex")
>		If Used("crsTmpDex")
>			Select *	;
>				, Cast(Strconv(Strconv(index_keys,6),2) As Varchar(160))  As Keys	;
>				FROM crstmpDex Into Cursor crsGotDex Readwrite
>		Endif

>
>Or, when writing a .csv file in UTF-8,
>

	FWRITE(nHandle, 0hEFBBBF)
>	lRet = lRet AND FWRITE(nHandle, cResult) > 0
>	SCAN &cScanClause
>		lcMerge=TEXTMERGE(cMergeTemplate)
>		lcMerge=STRCONV(lcMerge,1)
>		lcMerge=STRCONV(lcMerge,9,nCSVCodePage,1)
>		FWRITE(nHandle, CHR(13)+CHR(10)+ lcMerge)
>	ENDSCAN

>
>
>>>
>>>Can you try sending this: "абвгдђежзијклљмнњопрстћуфхцчџш"? I guarantee none of the characters are accented.