> **Rubberduck version information**
Version 2.4.1.4627
OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64
Host Product: Microsoft Office XP x86
Host Version: 10.0.6771
Host Executable: MSACCESS.EXE

**Description**
Upon opening the VBA Editor and clicking the Rubberduck "Parse" button, Rubberduck completes the parse with a Parse Error on two lines of valid VBA code, both with different, unrecognized syntax.

**Parse Error 1:** extraneous input '_\r\n ' expecting '-'
When I doubl

> **Re 1**

Rubberduck already has a `lineSpecialForm` for the peculiarities of that syntax. It can be seen here: https://github.com/rubberduck-vba/Rubberduck/blob/2925035f5210cb7f56792554a43f6e44052acb82/Rubberduck.Parsing/Grammar/VBAParser.g4#L574

It seems that we're somehow failing to correctly parse that as a lineSpecialForm. Could you try playing around with the syntax there to make the error go away?
If you find semantically equivalent code that parses, it might give us more informat

> Thanks for reporting this! :+1:

Indeed, `Line` syntax is essentially special-cased, both in Rubberduck's and VBA's parsers. Thanks for reporting this! The problem seems to be with the line continuation character though, which we might have forgotten to account for in that specific - I can confirm that the code correctly parses without the line continuations.

https://github.com/rubberduck-vba/Rubberduck/blob/2925035f5210cb7f56792554a43f6e44052acb82/Rubberduck.Parsing/Grammar/VBAParser.g4

> **Re 1**

Rubberduck already has a `lineSpecialForm` for the peculiarities of that syntax. It can be seen here: https://github.com/rubberduck-vba/Rubberduck/blob/2925035f5210cb7f56792554a43f6e44052acb82/Rubberduck.Parsing/Grammar/VBAParser.g4#L574

It seems that we're somehow failing to correctly parse that as a lineSpecialForm. Could you try playing around with the syntax there to make the error go away?
If you find semantically equivalent code that parses, it might give us more informat

> If I remove line continuation from each of my `Line` method calls, the parser now complains:

extraneous input ',' expecting {EOF, ':', REM, NEWLINE, "'", WS, LINE_CONTINUATION}
and puts the cursor after the right parenthesis and before the `, , B` in this line: (and all other such lines)

Me.Line (ctl.Left, ctl.Top)-(ctl.Left + ctl.Width, Me.Height), , B

This is in the `Detail_Print` event of a Report, where `Me` is and Access.Report, and `ctl` references an Access.Control.

Tha