Can't Add Object to Sheet Protected as UserInterfaceOnly (140541)
The information in this article applies to:
- Microsoft Excel 97 for Windows
- Microsoft Excel for Windows 95
This article was previously published under Q140541 SYMPTOMS
In Microsoft Excel, when you programmatically protect a worksheet so
that you can make changes only with a Visual Basic for Applications macro,
and then run a macro, the following error message may appear:
Run-time error '1004':
Add method of <object> class failed.
CAUSE
This problem occurs when the following conditions are true:
- You use the Protect method for the worksheet and set the
UserInterfaceOnly argument to True.
-and-
- You run a macro that attempts to add a drawing object to the worksheet.
Drawing objects include graphic objects, pictures, embedded objects, and
embedded charts.
WORKAROUNDMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
To work around this problem, unprotect the worksheet before adding the
drawing object, and then reprotect the sheet, as in the following
example:
Sub AddObject()
'Unprotect the Sheet.
ActiveSheet.Unprotect password:="pwd"
'Add a drawing object.
ActiveSheet.Rectangles.Add 0, 0, 100, 100
'Protect the sheet again with "UserInterFaceOnly."
ActiveSheet.Protect password:="pwd", userinterfaceonly:=True
'The macro can continue making changes to the "UserInterfaceOnly"
'protected worksheet other than adding drawing objects.
ActiveSheet.Range("A10").Value = "Hello World"
End Sub
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. This problem no longer occurs in
Microsoft Excel 2000.
Modification Type: | Minor | Last Reviewed: | 8/17/2005 |
---|
Keywords: | kbbug kbdtacode kberrmsg kbfix kbProgramming KB140541 |
---|
|