No. The error is not caused by any code that I wrote. According to several articles, it results from repeatedly opening the same table using different aliases or by repeatedly requering the same view.

The error occurred when I tried creating a parent child form containing three children. The process threw the error. The error prevented the form from being created. The form has a parent with three children, each on a different page. Two of the pages are made up of parent/children/grandchildren/great-grandchildren/ two great-great-grandchildren.

Each of the two pages "share" the same great-grandchildren and great-great-grandchildren. They are "shared" using different views on each of the two pages. I'm thinking that its this "shared" arragement that's causing the issue, tho I'm a bit confused since the articles say the bug was resolved in VFP 6 and 7.