Still have to try this, but looks great.

Thanks

Did test it today.

On "Dim Box as Box" received error
"By user defined object type not defined"

Changed it to "object"

After that "type don't match on "colBox.Add oBox, 1"

The reason you are getting those errors is two-fold:

1) Do you have an object named Box or a class named Box?  If not you need to change the word Box to your object or class.  If you are using a "Box" object from somebody else, you need to specify what the type of that object is.  The code given is generic in nature.  I could have used "Giraffe" instead of "Box" as long as my code can draft up a giraffe object"

2) Since you changed the dim oBox as object, you then drafted up an object that is set to nothing when you hit the = new Box code (related to problem #1). You can't add a variable that is set to nothing to the collection.

Here are the typical procedures for drafting up an object

1) Create a class that represents that object.
Using your Box example, I would create a class called clsBox.
clsBox
Property Width
Property Height
Property Color
Property HasRoundedCorners
Property Is3D

2) Somebody may have already built a Box class for you that you'd like to use (say perhaps Excel has a box object called ExcelBox that needs your needs).  In this case, you don't need #1 above.

3) You draft up a box object by dimensioning a variable as that type of object. In case #1 you would use Dim oBox as clsBox.  In case #2 you would use dim oBox as Excel.ExcelBox.

4) You instantiate a new box object by performing the following:  In case #1 you would do set oBox = new clsBox.  In case #2 you would use set oBox = new Excel.ExcelBox (note Excel doesn't have an ExcelBox object as far as I know, it is just an example).

The collection is separate from these instructions.  It simply can take several object of the same type or different types and put them in a common holding area as long as the opbject is set to something (i.e. oBox not is nothing).

The Boxes are retangles from the tools menu MS ACCESS.

Sorry I look a little bit stupid here, it has been a very long while, programming.

To explain you what I want to do is.

I have several of those retangles. They change from red to green and back due to occupied or open.

instead of cycle through every single one of them. I like to call them from the collection, this saves a lot of input, just by givving those objects only one name with an index. The boxes (retangles) are called "bxbaan1" to "bxbaan8". So as you wrote the object is already created.

I did put a watch on it. The oBox is filled with "bxbaan1" caused by the set command.

After this it stops by the row where the oBox needs to be added to the collection.
Here is where the "types do not match" comes up, before it can go to add the second one.

Sorry to bother you, I appreciate your help.

After doing some research, I discovered that Access Boxes are based on a hidden interface called  _ControlInReportEvents so you can't drum up a new box, it has to be one already in existence.  I think this is what you intended anyway.  By the way, the Box type is actually a Rectangle.  Anywho, here's the code I put into place in form_load and it works fine (box27, box28 are boxes on my screen, your names will of course change):

    Set colBoxes = New VBA.Collection ' put this in general declarations of the module so you can access it anywhere in that module

    Dim oBox As Rectangle
    Dim colBoxes As Collection
   
    Set oBox = Box27
    colBoxes.Add oBox, oBox.Name
   
    Set oBox = Box28
    colBoxes.Add oBox, oBox.Name
   
    MsgBox colBoxes(1).Name
    MsgBox colBoxes(2).Name
   

Then to get a box out, you can use set oBox = colBoxes("Box27"), then set oBox.backcolor = vbred, etc.