>>Hello All,
>>
>>I have a user who is getting a message which reads "Fatal error 171 while attempting to report error 171"
>>
>>I have Google'd this and it seems to have something to do with a middle eastern language setting. I asked the user about it and they say they are using Windows 7 in English mode but did install an Arabic language pack to support Arabic writing.
>>
>>Any suggestions on how to overcome this?
>>
>>Thanks
>
>The client reports that running the application on the same computer but under a virtual machine works OK. So it seems to be something to do with the Arabic language pack. Does anyone have a suggestion on this issue (besides the comedic)?

Not sure if this would be of any help, but I've come across situations where FoxPro code would give weird errors when run in Chinese, Japanese and Korean -- all of which happen to have some form of double-byte encoding. In those langauges some of the character values in the 0x80 - 0xFF range are used as "lead-in" codes for two-byte character sequences. The problem occurs when you have string literal that contain any of those character codes. If the final byte in the string literal happens to be one of those "lead-in" codes, the ending quote is "eaten", resulting in some form of error during runtime (typically it's an error indicating a non-terminated string value, though I've seen on occasion other errors depending on the context). In my particular case it was simply a matter of avoiding string literal with those codes, and simply construct by concatenation and CHR() expressions.