Misleading Grouping Claim

[Deleted]

Critique: Microsoft Access Rectangle Object Documentation – Misleading Grouping Claim​

Hi everyone,

I’ve come across an issue in the Microsoft Access documentation for the Rectangle object (Microsoft Learn, dated 09/13/2021) that I think could mislead developers. I’d love to hear your thoughts.

The Problematic Text​

The documentation states:

"You can move a rectangle and the controls in it as a single unit by dragging the mouse pointer diagonally across the entire rectangle to select all the controls. The entire selection can then be moved to a new position."

This wording implies that a Rectangle control acts as a container that groups controls within its boundaries. In reality, that’s not how Access works.

Why It’s Misleading​

• No Special Grouping Functionality: The described behavior is just standard group selection in Form Design View. You can select any controls—inside or outside a Rectangle—by dragging a selection box or using Shift-click. The Rectangle itself doesn’t create a grouping link.
• Implied Container Role: The phrase “controls in it” suggests the Rectangle behaves like a Tab Control or Option Group. But:
  
  • Dragging the Rectangle alone moves only the Rectangle, not the controls inside.
  • In VBA, controls inside a Rectangle still have the form as their .Parent, not the Rectangle. For example:
    
    

    MsgBox Me.Text6.Parent.Name

    This returns the form’s name (e.g., "Form3"), confirming the Rectangle isn’t a programmatic parent.
• Sequence Misconception: Some sources suggest drawing the Rectangle first and then placing controls inside it creates a grouping link. I tested this in Access 2021—it doesn’t. Controls don’t move with the Rectangle unless explicitly selected, regardless of drawing order.

Testing the Behavior​

In Access 2021, I tried the following:

1. Drew a Rectangle control.
2. Added a Text Box and Label inside its boundaries.
3. Dragged the Rectangle’s border—only the Rectangle moved.
4. Dragged a selection box over the Rectangle and controls—they moved together, but that’s just standard group selection.

This confirms the Rectangle is purely a visual element, not a container.

Why This Matters​

For new developers, the documentation could cause confusion by suggesting the Rectangle has grouping capabilities. In reality, it’s just a drawing tool, and the behavior described is nothing more than standard selection.

Call to Action​

Has anyone else noticed this misleading wording? Have you tried using a Rectangle as a “container” based on this guidance, only to discover it’s just group selection?

I’m considering submitting feedback via the Microsoft Access Feedback portal to suggest a revision, perhaps along the lines of:

“A Rectangle is a visual control for drawing shapes. To move it with nearby controls, select them together using a selection box or Shift-click, as with any group of controls.”

What do you think? Have you run into similar issues with Access documentation? Let’s discuss!

 

[DHookom]

I don’t find it misleading. I don’t think it mentions “container” and it accurately describes “select all the controls”. I’m happy with the help text as you quoted it and have always expected the behavior.

 

[isladogs]

Whilst I understand your point of view, I'm inclined to agree with Duane.
However, if you feel strongly about it, I would suggest a better approach than the Feedback Portal

As I've recently discovered, anyone can suggest edits to a MS Learn page. To do so, click on the ellipsis (...) then click Edit
This will take you to a GitHub page where you can suggest changes to the text.
Whatever you enter won't change the page directly. It will be reviewed and if accepted, the content will be updated.
You will receive feedback from GitHub on whether your suggestions are accepted or rejected.

Hope that helps.

Coincidentally, I'm about to suggest a number of edits to form controls & events . . . but this isn't one of them

 

[June7]

I agree that rectangle is not a "container" and this selection of controls is no different for any "group".
I am not sure users of any level will be misled, however, perhaps better wording instead of "in it" would be "bounded by it".

 

[sonic8]

"You can move a rectangle and the controls in it as a single unit by dragging the mouse pointer diagonally across the entire rectangle to select all the controls. The entire selection can then be moved to a new position."

This suggests that a Rectangle control acts as a "container" that groups controls within its boundaries, allowing you to move them by dragging the Rectangle. However, this is not accurate and misrepresents standard Access behaviour.

Strictly speaking the documentation is correct and precise.
If you actually deal with an container control, its child controls will be on the container control, not in it. - Microsoft is using this terminology consistently.
I agree that the wording in the documentation has some potential to mislead an inexperienced reader, but, as the very same sentence includes instructions to handle the operation correctly, I don't think this is a major issue.

To improve the it, I would change the documentation text so say "within its boundaries" instead of "in it".

Has anyone else noticed this misleading wording in the Rectangle documentation? Have you tried using a Rectangle as a "container" based on this guidance, only to find it’s just group selection?

I've tried to use the Rectangle as container multiple times. This had nothing to do with the documentation but was my own intuitive and incorrect assumption.

 

[June7]

It's my experience if control does not get positioned within tab page, it is actually just a control on form sitting on top of tab control and that's why it shows "on each tab", although if there is a subform on page it could be covered by that. If you see a control like that, move the tab control and see if errant control moves as well. Never has for me.

 

[isladogs]

Agreed. Controls can only be placed on a tab control page and never on the tab control itself. When placed incorrectly, the added control is on the form itself behind the tab control
@missinglinq explained it perfectly back in 2016 in that other referenced thread and Pat also got it right back in 2022

 

[LarryE]

I have always thought of it as just a picture frame to frame things. You can make it different colors and different sizes and make the frame different widths, but it is still just a frame.

 

[The_Doc_Man]

Heck, that "diagonal drag-n-drop" is how I align my forms all of the time. AND when you do that and have the properties panel up, you can manually enter the size of a particular property. So, for example, I do that multi-select on a bunch of labels and set their LEFT and HEIGHT properties all at once. I don't use the LAYOUT feature because I have found it to sometimes be a bit finicky, particularly when trying to add one more control to something already in a layout.

 

[June7]

The only way I have been able to multi select all the controls inside a box is to hold down the shift key and click on each control I want to drag, as can be seen in the image below.

I am able to multi-select all controls, including the rectangle, by "sweeping" without shift/click.

 

[GPGeorge]

PowerApps allows you to select a number of controls on a screen and create a group on them. Some properties of the group then apply to objects which are now part of it. One of the most useful I've found it to make the group visible. All of the members of that group are displayed or hidden without having to do so for each of them.

That would be a really cool feature to have in Access.

 

[GPGeorge]

I use the tag property in code for grouping related controls to make them visible, hidden, locked, unlocked, clear their values, etc.

Same idea, but more code required I would expect.

 

[GPGeorge]

Private Sub GroupVisibility(GroupName As String, Visibility As Boolean)
 
Dim ctl As Control
 
   On Error GoTo locErrorHandler
 
   For Each ctl In Me.Controls
      If InStr(ctl.Tag, GroupName) > 0 Then ctl.Visible = Visibility
   Next ctl

locExitHere:
   Exit Sub

locErrorHandler:
   ErrorHandler Me.Name, "GroupVisibility"
   If gErrorResponse = 1 Then Resume
   If gErrorResponse = 2 Then Resume Next
   Resume locExitHere

End Sub

Simple enough.

But with a true Group, it would be:

Me.GroupofControlsName.Visible = visibility

and no need to poll all of the controls for the presence of the tag.

 

[June7]

Don't know what else to tell you. Still works for me. Mouse left click inside or outside then sweep.
Using Access 2020.

 

[June7]

There's a difference between dragging a rectangle object, and dragging a container.

If you start drawing a container outside a rectangle and sweep through the rectangle, then it will grab the rectangle and controls in it.

However, If you drag a rectangle with controls indide it, then it just moves the rectangle without grabbing the controls, regardless of Access 2020 or other edition.

Test it and let us know your results.

I don't disagree with the difference. However, I was not addressing treating rectangle as a "container", I was addressing selecting multiple objects by click/sweep. I thought your assertion was that the rectangle could be selected along with other objects only if the sweep began outside the rectangle, per your comment "That only works if you start sweeping outside the box, as can be seen in the image below. If you start sweeping inside the box, then it just moves the box, but does not grab the controls."

That is what I objected to. Sweep can begin inside rectangle and still select objects.

 

[isladogs]

You have arranged the rectangle at the front so only that is selected when you are inside it.
Move the rectangle control to the back. Then it will behave exactly as @June7 described.

 

[June7]

In my testing, it worked with rectangle positioned in front or back. In either case, have to click on "blank" space. Video in zip folder.