>>I am curious to know which method you decide to use in the end, and why.
>
>Following the problems with removing objects, I made a modification to create unique names for the objects - the state of the object (screen position etc) is stored in a table, so I'm using the record number as a suffix to a base name. Having made the required changes, I thought I would leave it that way.
>
>I still like the idea of being able to create "anonymous" objects (as with CreateObject()) that do appear on the form & using a reference for access (could be an array for multiple objects). It seems to me that having to create uniquely named objects for display on a form & removing them by name, goes against the grain of OOP.
Yes, I like the array approach too, because of its utter simplicity (in theory!), and, while I am not so sure about OOP-principles, it seems weird to have to use a unique name for each object.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
