> Thanks Vladimir.
>
> I use Windows 98 Arabic enabled. The original tables were made in DOS system with may be some Arabic utility. To test I opened two such tables in my computer with English Windows ME. After noticing the problem with arabic text, I closed the files and opened the same in another PC with Arabic enabled Windows 98. But text displayed the same. Is it because I opened the files first in english Windows? In that case I can bring the file from my client and check again.
>
> Regards,
>
> Benny
>
>
> > Hi Benny,
> >
> > The proper codepage for Arabic data in tables is 1252. Perhaps the problem is not only in the codepage setting. Also you should use proper version of Windows.
> > It may be Arabic Windows 98, Arabic Enabled Windows 98 , Arabic Windows ME, Arabic Enabled Windows ME or Windows XP with special Language Pack.
> > What version of Windows do you use?
> >
> > Best regards,
> > Vladimir


Hello

I have a great solution for these kind of problems.

As for as i concerned the the arabic text is entered with MA20 supporting software (old 16bit),
what u have to do is just open that table, u can find some ascii chars, execute that MA20 support software and see the same table, u can find all text in arabic. so u just create a table that takes each arabic letter into a defined ascii code. then u get all the text into predefined (windows supported) ascii chars. then creat another table in VFP which have old_char and New_char fields and its windows arabic data. then write a routine that converts eaach char of old arabic text into windows arabic text.

its so simple man, but remember keep numbers intact.