Our company is about to write an international application using SQL Server as the back-end and VFP as the middle tier. We have already discovered that Visual Foxpro does not handle unicode very well. For example, 'ntext' data type is converted to C(255), yet 'text' is converted to Memo. And the TABLEUPDATE does not handle the 'nvarchar' and 'nchar' data types correctly (it puts a CHR(0) at the end and leaves all the trailing blanks in the field).

Has anybody found any good work-arounds to these problems? Are there any other pitfalls that we should be watching out for? We would really appreciate any advice or suggestions anybody could give us.

Thanks.