Hi Gary,

>1. The forms seem to be really releasing, i.e., _screen.forms increments and decrements as it’s supposed to. When a form is released the _screen.formcount goes down and the name disappears from the _screen.forms collection.

A safer way to find out if a form is releasing is to track Init and Destroy events. When an object remains in memory in almost all cases its Destroy event is not firing. Dangling references can be the result of FOR EACH loops on a collection without the FOXOBJECT clause,.

>2. The problem form has a pageframe with nested containers and controls, but even removing the entire pageframe makes no difference in the behavior

Could it be something in the dataenvironment? Maybe some form is locking a record and not releasing the lock which - for some unknown reason - confuses VFP. Other than that my only idea would be to remove one piece of the standard framework at a time until the form behaves properly.