Alan,

The question is probably not why this doesn't work in VFP 7. It doesn't work in VFP6 (SP3), VFP5, or even FoxPro 2.6 for DOS, either. Something else must be going on here. It might be helpful if you could post the actual contents of your memo field as well as the actual code you're using to assign it to a memvar and do the BROWSE.

-Rick

---

>Has anyone run into this problem? I just converted an app from vfp6 to vfp7 (the vfp6 version was an update from fpw26), and one of the ways the app handles browse screens is to keep the field list in a table. So, there is a memo field containing something like the following:
>
>cl_claimno :H="Claim No", ;
>cl_sfx :H="Suffix", ;
>cl_org :H="Organization", ;
>cl_cover :H="Coverage"
>
>There is more, but this is enough for discussion.
>
>This information is loaded into a variable (call it x), and the browse is called with:
>
>Browse Fields &x ;
>etc. etc.
>
>This results in a syntax error. It worked fine in VFP6, but in 7, what happens is that the macro is expanded as one long line BUT THE SEMICOLONS ARE INCLUDED!
>
>Clearly then the syntax really is incorrect and obviously this was not an issue in VFP6. Deleting the semicolons in the memo field clears it up, but now I fear I have to rummage through the entire system looking for similar situations where a macro might be expanded from information in a table memo field.
>
>Maybe this is documented somewhere and I've just plain missed it. Maybe there is a flag somewhere?
>
>Does anyone have any info on this?
>
>Thanks up front.
>
>Alan