In our VB6 application we have a lot (>300) of (large) classes where various properties are marked as Public Get and Friend Let/Set. This is so that the DLL can load the objects and set the properties but they become readonly to the outside world.

We have also come up with an alternative - add a Friend Property Set Writeable() As Boolean. This would enable us to test within the myriad properties whether updates are allowed. The "Parent" can then enable,make and then disable update, whilst since it would be a friend, the outside world would not be able to update the class.

* =?Utf-8?B?RmlsdGh5Wm9tYmll?= <anonymous@discussions.microsoft.com> scripsit:
[quoted text, click to view]

Currently, 'Property Get' and 'Property Set' must have the same
modifier. I would put the 'Friend' part into a 'Friend' method, the
public part into a 'Public' property.

--
Herfried K. Wagner [MVP]