a custom collection with code producing analagous worksheets(1) or worksheets("

Good Morning Folks,

I have created a custom collection which enables me to get at one of the items in the collection
but the code that i use is not as straightforward as worksheets(1) or worksheets("name")

my code requires writing, Floors.Floor(1). I would prefer writing my custom collection class that results in Floors(1) or Floors("name"). Code seems more understandable.

if you can see how to do that, instead of giving me the answer right away, please offer a hint
that gives me something to think with so that maybe i might be able to derive the solution you would have provided me. I will probably better remember the solution that way.

here is the code i have written so far that gets me at least Floors.Floor(1)

    With aHouse.Floors
        For i = 1 To .Count
            MsgBox "aHouse.Floors(" & i & ").Name = " & .Floor(i).Name
        Next
     End With

VBA executes the above by getting the collection, Floors
then executes a Floor Collection property of get Floor

       Public Property Get Floor(ByVal value As Variant) As Floor_Class  
            Set Floor = GFloorCollection(value)
       End Property

Thank you Rory.....let me chew on that hint....Thank you for hinting....

Good Afternoon Rory !

Thank you for responding.

I have been on an interesting journey that extended beyond "how" to "what do i want" and "why does my code seem so unclear"


Due to your hint (thank goodness you used italic font), i began the search. i found chip Pearson's article on Default member of a class as well as other similar articles.

Before I try coding with the default (as a learning experience), i have a few questions i want to run by you.

the default code (attribute) is not visible. Hence when things go wrong, i may not understand why. Is this a valid worry from your experience?

When i look at "worksheets.item(1)" i think , Given a collection (called Worksheets), give me the first item in that collection. That IS clear though more chance for error.
When i look at my code, Floors.Floor(1), i should think, Given a collection (called Floors) give me the first Floor in the collection. Not bad when i hear that explanation.

So, Rory, tell me what your choice is in programming. Do you use defaults and does their invisibility both you?

bil

BUT my example in my code is not as clear. Floors.Floor(1)



Another interesting thought

Originally Posted by whburling

my code requires writing, Floors.Floor(1). I would prefer writing my custom collection class that results in Floors(1) or Floors("name").

Hello,

so to make Floor the default property you must export and delete your class module
then add a specific Attribute codeline within the exported text file
then you can reimport the class module text file,
see the Item property sample within the attachment of this thread …

Thank you, Marc....
I do understand what to do after Rory gave me a hint. I did appreciate your example, however. Thank you.

Where i am coming from, now, is should i worry about using code (such as that used with Attribute) that can not be seen in the vba environment....since i am an absolute novice, i
need to hear from people who are more experienced...What is your opinion? do you might using code that can not be seen in the vba environment?

bil

Yes this kind of Attribute line is not a VBA codeline, used only by VBE at the import / export level …
So it is totally normal to not see this kind of line within the class module, take it as a specific parameter setting.