Given the choice of creating a With statement for use with an object or
an user-defined type (UDT), choose the object over the UDT. Because UDTs
are simple variables and not full-blown objects, they don't take the
same resource hit as objects do when you repeatedly access their
properties. For instance, consider the following code, which alters the
command button's settings when you click it:Private Type TBtnSettings
BgColor As Long
FontSize As Integer
Top As Integer
Left As Integer
Width As Integer
Height As Integer
End Type
Private mOrigSettings As TBtnSettings
Private Sub Command1_Click()
With Command1
.BackColor = vbGreen
.Top = mOrigSettings.Top - 100
.Left = mOrigSettings.Left - 100
.Width = mOrigSettings.Width + 200
.Height = mOrigSettings.Height + 200
.FontSize = mOrigSettings.FontSize + 4
End With
End Sub
Here, we could have used the With statement to reduce the number of
times we needed to manually type 'mOrigSettings'. However, as we stated,
by using the With statement for Command1 instead, our code becomes much
more efficient.
With statement precedence
By ElementK Journals, published on 14 Jul 2001
| Filed in
You might also like...
VB 6 forum discussion
-
CorelDRAW VBA: cdrTraceLineDrawing FAILS, producing single linear path instead of Centerline trace?
by dancemanj (0 replies)
-
client/server application using activex
by beautifulheart (0 replies)
-
System Error &H8007007E. The specifed module could not be found.
by swiftsafe (5 replies)
-
Invitation to take part in an academic research study
by researchlab (0 replies)
-
Send SMS with SMPP
by mmahmoud (0 replies)
VB 6 podcasts
-
Stack Overflow Podcast: Podcast #45 – Keeping it Sharp
Published 7 years ago, running time 0h54m
Our guest this week is Eric Lippert – language architect extraordinaire and famous for all his work at Microsoft in developing their languages Eric joined Microsoft right out of college and was originally working on VB It’s time for everyone’s favorite game: Name the Worst Feature of that Microso.
Comments