Fabio,

You explanation doesn't make any sense. Why would it be a problem for Visual FoxPro to alocate a buffer with 2*N bytes for NCHAR and NTEXT() but not for NVARCHAR?


Sergey,

Where I have said this?

Then:

1) NTEXT have a 2GB lenght, then VFP map it to memo, and use SQL_C_WCHAR

2) for NCHAR and NVARCHAR, if and only if VFP choice to build a char field
it use SQL_C_CHAR.

3) I do not say that VFP it has problems to construct a buffer of double length,
but then must construct a field of double length.
To this point the VFPT must choose:
to respect the parameter of the length or to respect the data content.

By design or by side VFP respects the length.

My opinion : this is another bug.

Fabio