Yeah, but just removing the ClearAllPoints line didn't fix the problem on its own
That was my first test. The SetParent(nil) was the second test and it stopped the error
So my wondering is that perhaps the SetParent(nil) was what resolved the problem in its entirety as if the blizz code is cycling through each frames child frames it now doesn't know about the one we have borrowed
Of course the combination of both is the fix .. will have to see if I get the error message again