Strings in array truncated in VFP 7 +

[Ryan]

Hi Foxpro Experts,

I'm turning here as a last resort as I'm having trouble debugging a
problem in a VFP6 applications that I've inherited.

Basically, we have an application which seems to have been written in
VFP6 (I see the string foxpro 6 in the compiled exe, and the dlls
provided with the exe are version 6). The oldest version of FoxPro
that Microsoft still provide via MSDN is v7, so that is the oldest
version I can use.

The problem is that throughout the program the developer has used
arrays to cache values from the database. He has done this using
SELECT..INTO array. The problem is that when compiled with VFP7+ the
strings returned from these arrays are being concatenated to a single
character. When the values are read from the database they're first
cached in a tabled called TemporarySql (not sure if that's a
convention?).

Does anyone have any idea as to what changes in VFP6 could have caused
this? According to MSDN there are no breaking changes between V6 and
V7, but somehow I don't believe Microsoft when they say that..

Any help would be greatly appreciated.

Cheers,
Ryan

[Dan Freeman]

Post by Ryan
Hi Foxpro Experts,
I'm turning here as a last resort as I'm having trouble debugging a
problem in a VFP6 applications that I've inherited.
Basically, we have an application which seems to have been written in
VFP6 (I see the string foxpro 6 in the compiled exe, and the dlls
provided with the exe are version 6). The oldest version of FoxPro
that Microsoft still provide via MSDN is v7, so that is the oldest
version I can use.
The problem is that throughout the program the developer has used
arrays to cache values from the database. He has done this using
SELECT..INTO array. The problem is that when compiled with VFP7+ the
strings returned from these arrays are being concatenated to a single
character. When the values are read from the database they're first
cached in a tabled called TemporarySql (not sure if that's a
convention?).
Does anyone have any idea as to what changes in VFP6 could have caused
this? According to MSDN there are no breaking changes between V6 and
V7, but somehow I don't believe Microsoft when they say that..
Any help would be greatly appreciated.
Cheers,
Ryan

I don't understand "concatenated to a single character". Concatenation,
by definition, means you end up with multiple characters. <s>

With every version of VFP, the compiler became more strict. Without
seeing an example of one of the queries and a clear description of the
result it will be difficult for anyone to offer a suggestion.

Dan