VBA Compile Error
Before running your code, the VBA Editor compiles the code. This basically means that VBA examines your code to make sure that all the requirements are there to run it correctly – it will check that all the variables are declared (if you use Option Explicit which you should!), check that all the procedures are declared, check the loops and if statements etc. By compiling the code, VBA helps to minimize any runtime errors occurring.
(See our Error Handling Guide for more information about VBA Errors)
Undeclared Variables
If you do not declare variables, but your Option Explicit is switched on at the top of your module, and then you run the macro, a compile error will occur.
If you click OK, the relevant procedure will go into debug mode.
Alternatively, before you run your code, you can force a compilation of the code.
In the Menu, select Debug > Compile Project.
The compiler will find any compile errors and highlight the first one it finds accordingly.
Undeclared Procedures
If you code refers to a procedure that does not exist, you will also get a compile error.
However, if the procedure – NextProcedure does not exist, then a compile error will occur.
Incorrect Coding – Expected End of Statement
If you create a loop using For..Each..Next or With..End With and forget to and the Next or the End With… you will also get a compile error.
The same will happen with an If statement if the End If is omitted!
Missing References
If you are using an Object Library that is not part of Excel, but you are using the objects from the library in your variable declaration, you will also receive a compile error.
This can be solved by either Late Binding – declaring the variables are Objects; or by adding the relevant Object Library to the Project.
In the Menu, select Tools > References and add the relevant object library to your project.
VBA Coding Made Easy
Stop searching for VBA code online. Learn more about AutoMacro — A VBA Code Builder that allows beginners to code procedures from scratch with minimal coding knowledge and with many time-saving features for all users! 
VBA Code Examples Add-in
Easily access all of the code examples found on our site.
Simply navigate to the menu, click, and the code will be inserted directly into your module. .xlam add-in.
Name already in use
docs / docs / visual-basic / language-reference / error-messages / end-of-statement-expected.md
- Go to file T
- Go to line L
- Copy path
- Copy permalink
11 contributors
Users who have contributed to this file
- Open with Desktop
- View raw
- Copy raw contents Copy raw contents
Copy raw contents
Copy raw contents
BC30205: End of statement expected
The statement is syntactically complete, but an additional programming element follows the element that completes the statement. A line terminator is required at the end of every statement.
A line terminator divides the characters of a Visual Basic source file into lines. Examples of line terminators are the Unicode carriage return character (&HD), the Unicode linefeed character (&HA), and the Unicode carriage return character followed by the Unicode linefeed character. For more information about line terminators, see the Visual Basic Language Specification.
Error ID: BC30205
To correct this error
Check to see if two different statements have inadvertently been put on the same line.
Expected end of statement
The Expected: end of statement message is another common (and rarely helpful) compile error. Once again, all the message is telling you is that you have some sort of syntactical error in the statement. In Figure 12-6, the string literal "MyForm" at the end of the statement is highlighted, but that only tells you that the compiler got lost at that point.
Expected: end of statement compile error.
^ 12ChapExamples Modulel (Code)
1 (General) ] Sample
Public Sub Sample!)
Dim Answer As Integer
Microsoft Visual Basic
Expected: end of statement
The real problem with the statement in Figure 12-6 is the comma between DoCmd and OpenForm. The correct syntax for using the DoCmd object is
DoCmd.method.
where there’s a period — not a comma — between the first two words. The fix for the problem would be to replace that comma with a period, as follows:
Microsoft VBScript compilation error: Expected end of statement
I am trying to insert some records into MS Access Table with the help of below VB Script. But when am trying to execute it, it’s throwing Compilation error: Expected end of statement. Could someone please help me figure out where am I going wrong.
3 Answers 3
VBScript (as opposed to VBA or other dialects) does not support typed Dims. So
VBscript has no native OpenDatabase() function. You need to use ADO to connect to your Access ‘database’. First create a connection
Then determine the connection string and
The rest of your code should work.
Update wrt comment:
The error message:
prooves that the OT tried to write a VBScript (the addition of the misleading vba/access tags is (C) Pankaj Jaju).
So lets break down the real reason why this code doesn’t work.
You copied and pasted Visual Basic for Applications(VBA) into a .VBS(Visual Basic Script) file and expected it to work, I assume.
The problem with this is that VBA and VBScript are slightly different languages. Review the info section for both tags on stackoverflow when you get the opportunity.
For now lets just patch your code and maintain your DAO object so you don’t have to reconstruct your Database usage with ADODB.