Hi Cetin

Thanks for your contribution. I alway appreciate your views on the UT:)

> I would try keeping away from COM unless absolutely needed.

It is absolutely needed here. Of course, you might believe VFP is not suited for such tasks. I share you views that it's better to keep VFP at what is good at!

Well I had to do that. And the Fox did cope pretty decently with this messy requirements. A miracle, at times...

Yep, You wonder indeed how VFP, whose architecture is certainly not recent, could handle this complex com-based structures properly. It does except for the thing I mentioned, garbage not "collected" from dropped collections. I reckon storing these objects in collections is a no-go. Build them and have them stored in arrays and, should you need collections, use them as an integer pointer into your good old arrays...

That's my experience here. As I said, this is a bit specific to VFP. I remember building such complex collection-based code in python with zero problems. But yep, in python, build a UI experience is still much, much, much harder work than VFP!

Daniel