I came across this in Fox 2.6. I thought it was fixed in the later versions. Apparently it wasn't. As you pointed out you can use LOCAL to avoid this problem.
You can fill bug report at http://support.microsoft.com/Support/vfoxpro/report/report.asp

>I think I've come across what looks like a bug with the INSERT-SQL command. It's so obvious though that I can't help but think I am missing something simple.
>
>It appears that the APPEND BLANK and/or GATHER MEMVAR commands respect a memvar's scoping, whereas the INSERT INTO command does not. Hacker's Guide makes no mention of this as a bug, but I would have thought I wouldn't be the first person to come across this.
>
>In the code below in Junk1, I set up a scenario where I have memvars scattered data in a table. By default, these memvars should be visible to whatever Junk1 calls.
>
>Then, in Junk2, when I declare these same memvars as PRIVATE, I would expect them to be either set to .F. or at least undefined - anything but the previous values.
>
>The APPEND then GATHER command(s) seem to work correctly - they create a blank record. The INSERT command, however, still "sees" the values as created in Junk1.
>
>Making them LOCAL in Junk2 gives the correct behavior. What am I missing here?
>
>
< SNIP >