Experimenting with pulling dbfs into SQL database, via select * from openrowset(...), I've found that ALL of the memo fields have been migrated with an extra chr(0) in the end.

Googling a subject where your keywords are "null", "null terminated string", "vfpoledb" and such gives an incredible amount of fun, seeing how many completely unrelated things pop up, and an even larger amount of frustration.

So... the question: did anyone encounter this before? If not, is there a good place with information on how VFPOLEDB can be configured? Or, at least, what can go into the provider string to change this behavior?