It would seem that something is trying to write to the memo at the same time as VFP -- most likely during the save operation. I would expect that VFP does not commit changes to the SCX/SCT files until the user selects save; otherwise, it would potentially leave changes in limbo in the event of a VFP crash. So I would expect the programmers to have protected the SCX/SCT files by only updating at the save request (applying changes to a copy during edits).

We also know that VFP caches a lot of activity -- which may include PEME writes back to the form being edited. These may be cached and the save process of VFP may handle the PEME actions at times in an incorrect sequence due to unknown influences.

The amount of activity in PEME may also contribute -- you are doing a lot of things now. I would suggest turning off any activity in PEME that is continuous in nature or at a high request rate. I regularly use PEME but do not keep it active all the time. I use the standard property form for editing property values and PEME for managing the create/rename and access/assign settings and then close PEME. So I have not experienced any problems that you are having (not to say that PEME is the cause -- only a suspect at this point). If you do turn down PEME and the problems seem to go away or at a much less frequency, then PEME would be a strong suspect -- try incrementing the functionality to see if this problem reappears...


>Yes, PEME may be part of the problem, of course, as much as I hate to admit it.
>
>If so, it would be a miserable thing to diagnose, since the problem happens so infrequently, and even when PEME was not used to modify anything on the form. It's hard to imagine, under those circumstances,, what it might be doing to cause the problem.
>
>And yet, no other possible solution has been suggested either.
>
>>Try working without using PEME -- possibly something in PEME is interferring with the normal saving that VFP would be doing. At least try stopping PEME before saving.