Comments on: Properties and Objects

By: Jamie Collins

Jamie Collins — Thu, 15 Jul 2010 08:52:00 +0000

Dick, I like your approach i.e. you start by saying, “Here’s the code I want to run and have it work” and then you actually write go ahead and the ‘client side’ code before you’ve even started the ‘server side’ (object model) code. This is absolutely key to getting abstraction correct.

Great series on class modules, BTW. As I may have already hinted, I fully expect articles in the near future on 1) safely referencing a parent object from a child (e.g. add a Public Property Get Parent() As CWorksheet to the Range object) and 2) subclassing (e.g. a Sheets collection that returns objects of type CWorksheet, CDialogSheet, etc). If not I’ll threaten to dust off my notes and do it myself

By: Jan Karel Pieterse

Jan Karel Pieterse — Tue, 13 Jul 2010 15:01:00 +0000

I tend to use it without the wsf and check what I get returned (typename). That way I don’t have to use an error handler or on error resume next stuff. A matter of taste or habit I think.

By: Dick Kusleika

Dick Kusleika — Tue, 13 Jul 2010 14:26:00 +0000

That's right Rob. Strangely, to me, there is no Range property of ActiveWorkbook, which I thought would have also pointed to the ActiveSheet.

JKP: That's an interesting difference. I wonder how that's coded in Excel. That is, I wonder if it's an accidental consequence or if they intended that way. A few years ago, Tushar convinced me to use WorksheetFunction whenever referring to one. His argument, if I recall, was that it's more readable. And since I have no problem trapping errors with On Error for other things, I shouldn't have a problem using it here. That was persuasive to me, so I've been spelling it out ever since.

By: Jan Karel Pieterse

Jan Karel Pieterse — Tue, 13 Jul 2010 12:24:00 +0000

Application.Transpose is NOT the same as Application.WOrksheetFunction.Transpose.
Take this example:
- Enter 1,2,3 in cellA1 to A3
- Enter =NA() in cell A4
- run this routine:

Sub test()
Dim vResult As Variant
vResult = Application.Sum(Range("A1:A4").Value)
MsgBox TypeName(vResult)
vResult = Application.WorksheetFunction.Sum(Range("A1:A4").Value)
End Sub

Note the difference in how the error is handled

By: Rob van Gelder

Rob van Gelder — Mon, 12 Jul 2010 21:25:00 +0000

I never knew there was a Range property of the Application object. I guess it makes sense, since Range("A1?) = 123 is allowed.

I did a test, and set up a worksheet specific name in both Sheet1 and Sheet2. eg Sheet1!MyName, and Sheet2!MyName

Then from vba:

?ThisWorkbook.Worksheets(1).Range("MyName")
Sheet1
?ThisWorkbook.Worksheets(2).Range("MyName")
Sheet2
Sheet1.Activate
?Application.Range("MyName")
Sheet1
Sheet2.Activate
?Application.Range("MyName")
Sheet2

Looks like Application.Range hooks the ActiveSheet range.