VB once again
Author
Whats the standard way to compile in VB 6.0?? Is it Run _ Start with full compile?? I wanna make an .exe Anyhow I do that and I get a compile error on this line:
Private Sub cmdPrint_Click()
If Text1.Text <> "" Then Printer.Print Text1.Text
Printer.EndDoc
End If
End Sub
it says end if without block if
Does anybody know what I did wrong??
It should look like this:
Since you put the line "Printer.Print Text1.Text" on the same line as the If...Then statement, VB assumed that the entire If...Then block was on one line. When it reached the "End If," there was no If to End.
There is also an option File->Make EXE in the menu.
Private Sub cmdPrint_Click()If Text1.Text <> "" Then Printer.Print Text1.Text Printer.EndDocEnd IfSince you put the line "Printer.Print Text1.Text" on the same line as the If...Then statement, VB assumed that the entire If...Then block was on one line. When it reached the "End If," there was no If to End.
There is also an option File->Make EXE in the menu.
Just press F5 to run, or ctrl-F5 if you want to be sure it all compiles first.
Also, you should never compare a string with an empty string in VB. It creates an instance of the empty string everywhere you write "", and it is far slower.
It is much more efficient to write:
Also, you should never compare a string with an empty string in VB. It creates an instance of the empty string everywhere you write "", and it is far slower.
It is much more efficient to write:
Private Sub cmdPrint_Click()If Len(Text1.Text) > 0 Then Printer.Print Text1.Text Printer.EndDocEnd Ifthough you could also have written this which is not as nice...If Len(Text1.Text) > 0 Then Printer.Print Text1.Text : Printer.EndDocQuote:Original post by iMalc
Also, you should never compare a string with an empty string in VB. It creates an instance of the empty string everywhere you write "", and it is far slower.
Not true in this case. VB would know that Text1.Text is a property of the object Text1. If Text1 does not exist, VB will not create it. The program would die with an error.
Simple variables will get created on the fly if Option Explicit is not specified. The best practice is to use Option Explicit and dim all your variables.
DaTroof, that really had nothing to do with the quote you responded to.
He's talking about writing in the literal "", as in:
as opposed to:
He's talking about writing in the literal "", as in:
If Text1.Text = "" Then ' Do some stuffEnd Ifas opposed to:
If Len(Text1.Text) = 0 Then ' Do Some stuffEnd IfQuote:Original post by daerid
DaTroof, that really had nothing to do with the quote you responded to.
He's talking about writing in the literal "", as in:
Ugh. My mistake. From now on, coffee first, then forums.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
