>>>>Bruce,
>>>>
>>>>Your experience (Ooooops below) seems to be at odds with the KB article, which states (just to remind you) "By default, the embedded copies include the source code of the methods and procedures as a debugging convenience. . .".
>>>>
>>>>I might have allowed that "debugging convenience" might have included some difficulties with ERROR-type routines' coding, but if users *must* have access to SCX., VCX., etc then these KB articles are even more POORLY written than I have been allowing for.
>>>>
>>>>Pretty sad situation, actually
>>>>
>>>
>>>You're right, I read that also, and assumed it was no big deal. But evidently it's a very big deal, unless there's something I don't know about. Anyone else try this out? You have to test it in an environment where the EXE cannot possibly locate the SCX, etc., files...
>>
>>Note that the object code for forms and classlibs are stored in the .scx and .vcx files (in VFP 3 & 5 anyway). If you delete the .scx file you delete everything needed to run that form.
>
>That's what I thought...
>
>>You can delete the source code (methods field).
>
>Do you know an easy way to do this?

I haven't really tested this, but this may work:
use myform.scx
replace Methods with ""

Just create a file that does this for all your scx files. If you wanted to automate the process, you could just use adir() to return an array of all the scx files and then use

for each x in array
    use (array[x]) excl
    replace all Methods with ""
endfor

Note: Make sure you do a build all before doing this so that the objcode field is up to date. Vcx files are mostly identical to scx files and this procedure should work.

Peter