I've got a form that started behaving oddly some time after I created a form set and added a second form. At this point, once I run the form (set), and then close it, I cannot modify it -- I get a "file in use" error, and cannot open it for editing unless I first exit from VFP completely. I did notice that the object variable, which I'm aware is left behind in memory after form execution (unless explicitly cleared) is listed a bit differently than usual. Below is the result of DISPLAY MEMORY -- the first line is my badly-behaved form, and the second one is from a healthy form.

COMPREP1 Pub O FORMSET
CONDOSCD Pub O .NULL.
2 variables defined, 0 bytes used

Instead of containing ".NULL." my bad form object variable contains "FORMSET" which I guess indicates that VFP thinks it's still active somehow. I am explicitly releasing everything in the form set's Unload method, but to no avail.

(If it's useful -- initially when this happenned, the variable representing the window for the second form in the set was left floating in memory. When I did a manual RELEASE WINDOW FORM2, I was then able to edit the form set. At least I'm pretty sure that's what happenned -- but it's getting late and I'm tired!)

And not to mention the "this program has performed an illegal operation and will be terminated"s that this formset has apparently been causing...

Any suggestions? TIA.