>>>No, I don't think it's the problem. I cleared it again and re-opened - so far, so good.
>>
>>Find the relevant record in your foxuser.dbf, delete it and pack the table. You can actually delete a lot of records which relate to specific windows (one per .prg, class, scx... lots of records).
>
>Do you know how can I identify these records? I got this same problem again...

Use it exclusively, go bottom, browse, and you'll notice many records with WINDMODIFY and such keywords are in the fields. Look into the memos on those records. Some of them are binary, but others are not - and you'll notice that the not-binary ones hold the names of files or other code snippets you were editing. You can then selectively delete (...for id="..." or some such criteria), then pack. Try to find those that refer to single files and to skip those that refer to a class of files (like *.prg).

I haven't done this in a long time, so I forgot specifics, and I have one foxuser per project anyway, so they don't get cluttered so fast. I guess when the .fpt grows over a dozen megabytes, it'll be time to purge.