Has anyone had a problem with CHR(0)s appearing in SQL pass-through cursors? MSDN has identified this problem, and have suggested the following "solution":

SYS (3050, 1, VAL (SYS (1001) ) )
SYS (3050, 2, VAL (SYS (1001) ) )

However this has a nasty side-effect of making VFP think it has more physical memory than it has. This has serious performance issues when dealing with large tables.

I wonder if this will be fixed in the next version of VFP (it hasn't in the SPs so far...)

Joseph.