why dim?

[jb3700]

would I ever need to ues or start with a dim? It always seams to work with out one. Foe example :

Sub Cake()

Dim jb As String


jb = InputBox("do you like cake? Yes/No", "CAKE")
If jb = "Yes" Or jb = "yes" Then
MsgBox "Go For It", , "GOOD"
End If

If jb = "No" Or jb = "no" Then
MsgBox "Whatever Bro", , "Go Home"
End If


End Sub

 

[shg]

See Declaring Variables

 

[jb3700]

yes I am aware that is to Declaring Variables, but the code works if you use the dim Dim jb As String or just use =. If i was to delete Dim jb As String and run the macro works the same.

 

[shg]

If i was to delete Dim jb As String and run the macro works the same.

I thought that was pretty clearly stated at the link:

By default, VBA doesn't require that you declare your variables using the Dim statement.

The article goes on to explain why you should even though it's not required.

 

[Joe4]

If you read the link that shg provided, it goes on to explain that if you make a typo like this:

[COLOR=#333333]jb = InputBox("do you like cake? Yes/No", "CAKE")[/COLOR]
[COLOR=#333333]If [/COLOR][COLOR=#ff0000]jd[/COLOR][COLOR=#333333] = "Yes" Or [/COLOR][COLOR=#ff0000]jd[/COLOR][COLOR=#333333] = "yes" Then[/COLOR]
[COLOR=#333333]MsgBox "Go For It", , "GOOD"[/COLOR]
[COLOR=#333333]End If[/COLOR]

your code will run without error, but it won't be doing what you expect it to (because of your typo).

If you use "Option Explicit", which forces you to declare all your variables, and you have a typo, the Compiler will catch it and alert you and not let you run the code until you fix it. So it greatly decreases your changes of typos and unexpected behavior.

Another thing not noted in that link, if we see code with no variable declarations, that is often a red flag alerts us that "this code was probably written by an amateur". You probably don't want that reputation (even if you are an "amateur").

 

[Kyle123]

It also makes your code faster

 

[shg]

And have a smaller memory footprint.