Actually, there are FOUR. There are ActiveX textboxes as well.
technically, the "textbox" Glenn refers to, IMHO, while called a textbox, is not really. It is a
graphical object. It is child object of the Shapes collection, but is a CanvasShape. Canvas because it IS graphical.
There is an AddTextBox method, but it can produce either a CanvasShape textbox, OR a Shapes textbox.
So....four:
CanvasShape textbox
Shape textbox
FormField textbox
ActiveX textbox.
All called textboxes. Which is why, in these threads I am so darn fussy about terms, asking what KIND of textbox when people use the term.
However, Tony's question is still valid. This is a design element. What is the design here? If the user is NOT putting input then why is there an object at all with text. Why not just have text? Generally speaking, again IMHO, textboxes should be for input. Otherwise, even when the contents are inserted by code, other objects ("other "textboxes") are a better choice.
If the text in this location is changeable, is data from a source, then there are certainly other ways to insert such text into a document. Bookmarks for one.
The original question was regarding locking portions of a document. Bottom line to that subject is that it is completely irrelevant if it is a textbox or not.
You lock portions of a document by putting the portion within its own section, then protecting that section for forms. Tools > Protect document. Protected sections do NOT have to contain formfields. Protecting for forms simply disables ALL edit and format changes within that section.
Perhaps if you precisely clarified your intentions we can suggest a good solution.
N.B. on UserForms textboxes should NEVER be used for anything other than user input. There is absolutely no point. If you are displaying text on a userform, even text derevied from other sources, or by logic, it should be a Label.
Gerry
See my
Paintings and Sculpture