You may have stumbled upon an issue with multi-byte characters. I presume you are using SQL Server 7.0 or SQL 2000 which added support for nchar, nvarchar and ntext data types. These data types are similar to char, varchar, text except they use two bytes to store each character of data. If you look at the table definition for say a char(10) field it will say 10. If you do an sp_help {table} you will see it says 20 for the field size. (I think it is sp_help that reports this!) because the field is 10 characters in size but 20 bytes are required.

The issue then is what does VFP do with these datatypes. We don't have a way to store a character in more than a single byte. Some transformation will have to occur.

I think I will test this out at home, but it may be difficult for VFP to handle these UNICODE characters.

Unless you need double-byte characters, you might want to switch to the normal datatypes.

It may also be that VFP can't do default mapping to field types and you will have to do it (once) in your view definition.



>When connecting to our SQL database using a remote VFP view, we get an error: DataType property for field 'SpecialInstructions' is invalid. 'SpecialInstructions' is a SQL ntext field.
>
>What do we need to do to convert this in the remote view to a VFP memo fields so that we can view it? TIA.