>Does it really make sense to assign top and left without a container in which to display a line?

Hi Lisa,

The reason it caused an issue in an app I'm involved in was that due to the fact that certain classes used to instantiate faster than others (line in particular used to be one of the fastest), Line was used as the basis for a class heirarchy. As the app developed one or more of the classes needed to hold onto a value for Top value, and rather than creating a property called nTop it was decided to use the Top property (because it came free of charge < g > ). In another example they were trying to create a memento/proxy class for some MS Office classes so that testing could be done without automation and ran into the same problem when "dimensional" properties (top, left, etc) were used.

If only VFP had a System.Object < g >, a "tabula rosa" ...

Thanks,