
Will work out better approach to handle it.Microsoft AppLocale is an utility that allows Windows users to run non-Unicode legacy (code-page based) applications in different language from system locale on Windows XP or Server 2003 without changing the system locale. Alternatively, I can setup a Windows 7 with English locale and use it to change the form instead of doing it on the server with Japanese


Migration to Visual Studio that support unicode will be better approach, perhaps.ĥ) I have opted to capture the memo content cursorAdapter Property into a text file and paste it back after saving the form. I have to pay Microsoft to fix a bug (or bugs) in their software? I suppose it is the end of line for VFP. Remote view does not have this problem.Ĥ) Paid hotfix for VFP. Thus, the requirement to change the Windows Server 2008 R2 non-unicode locale to Japanese in order to display Japanese text in VFP9 application.Ģ) I had tried to run VFP9 using AppLocale with Japanese and it has the same problem so most probably it is due to cursorAdapter builder class VFP9 which did not function well in Japanese locale. Whereas “Non-Corrupted cursorAdapter screen” is of the original content.ġ) Almost all of the forms are in English, but only a couple of forms need to have Japanese text. “Corrupted cursorAdapter screeen” is the memo content of cursorAdapter Property field of corruptedĬursorAdapter. Using USE command I opened the form as a table to check the Property of the cursorAdapter and I have attached in this email for reference. Alternatively, run VFP9 using AppLocale with Japanese to re-produce the problem.ġ) Run VFP9 in Windows Server 2008 R2 with Non-Unicode language set as Japanese or run VFP9 using AppLocale with Japanaese.Ģ) Open a form with cursorAdapter in DataEnvironmentĤ) Open it and it would prompt the error message CursorSchema: Syntax Error Hardware and Software Details: VMware server with Windows Server 2008 R2 with Non-Unicode language is set as Japanese and SQL 2008 Service pack 3.


However, doing the same in English locale, no problem at all, perhaps the translation done in Japanese locale messed up the cursorAdapter. When you try to open edit the form again, "CursorSchema: Its only happen when I use it with Japanese locale. I have a form with a cursorAdapter class in DataEnvironment in which when saved will corrupt the cursorAdapter object.
