For all those who might be interested in the original question I posted on this matter, after searching the MS KB, it turns out that this is a known bug in VFP 5.0 corrected in 5.0a ( which I have on back order ). The KB article gave no workarounds so if you run into the problem, the only solution is to get VFP 5.0a or use a different strategy in controlling the forms.

Bill