Comments on: Line Continuation Limit

By: Jon Peltier

Jon Peltier — Wed, 07 Nov 2007 17:04:00 +0000

Rob -

I was not aware of this capability. Thanks.

By: Rob van Gelder

Rob van Gelder — Tue, 06 Nov 2007 21:51:00 +0000

Jon: The VBA compiler is smart enough to allow consts to be dependent on previously defined consts.
This technique is quite handy for creating bitmask consts.

You can write code to impress your friends

Private Const gstr1 As String = "Your VBA version is "

#If VBA6 Then
Private Const gstr2 As String = gstr1 & "VBA6."
#Else
Private Const gstr2 As String = gstr1 & "not VBA6."
#End If

Sub test()
MsgBox gstr2

End Sub

By: Jon Peltier

Jon Peltier — Sat, 03 Nov 2007 15:06:00 +0000

Fencliff -

Are you confusing constants with variables?

By: Jon Peltier

Jon Peltier — Fri, 02 Nov 2007 18:42:00 +0000

Joshua -

The SQL query is just a string, right? You can create that string however you want. Did you split the line into multiple commands, as in Dick's example?

By: Fencliff

Fencliff — Fri, 02 Nov 2007 17:35:00 +0000

Regarding the solution:

* sString = "My dog "
* sString = sString & "has fleas."

You said you were building a constant string? I don't think this kind of method would compile with constants, you'd have to use and intermediary constant to build it.

* Private Const gstr1 As String = "My Dog "
* Private Const gstr2 As String = gstr1 & "has fleas."

In which case I think I would rather break my fanatic 80-column line requirement.

By: Joshua

Joshua — Fri, 02 Nov 2007 10:31:00 +0000

Yes, it’s really sucks how VB limits on how many line continuations to use. I have a very long SQL query which means I will need a lot of line continuations, but I ran into this error. Really sucks.

By: daniel

daniel — Mon, 18 Sep 2006 10:00:00 +0000

This sort of "lacking explanation" error messages remind me of 2 other MS bugs (sorry, functionalities) that make you waste half an hour in debugging until you realise the true meaning of the error and correct it in a few seconds:

- Excel automatation through VB6: Work on Column 255, then Column = Column + 1. Excel raises an error to the tune of "Excel cannot carry out the specified command" (or somthing like this). No mention why or no note of the 255 column limit...

- MS Access 2000 and over: Play with a access and hit 2 Gb during a query. Access will inform you that there is some sort of (random) error with your query, but nothing on the real error like the query could not complete and/or that Access has reached it's maximum filesize limit of 2 gb and you need to delete data or compact the database to continue...

Cheers,
Daniel

By: Web Surf

Web Surf — Wed, 22 Mar 2006 20:43:00 +0000

I wrote some code in XL 2003 and VBA,

My users with XL 97 reported "compile error in hidden module"

I tried saving my file as XL 97, it just said "File not saved"

After 2 days, I narrowed it down to the fact that different XLs have different allowed number of line continuations.

Gawd I wish the error messages made a bit more sense. Like maybe a line number where the error took place ? Or plain english error messages like "Too many line continuations"

By: Rick

Rick — Thu, 21 Apr 2005 08:45:00 +0000

Have you ever tried this site http://rafb.net/paste/ for posting code to newsgroups?

Here is an example:

http://rafb.net/paste/results/D1D7V491.html

By: Rob van Gelder

Rob van Gelder — Tue, 19 Apr 2005 07:34:00 +0000

Depending on which version of Excel you use, the line continuations limit is less.
See MSKB 141513 for the beef.

Occasionally I'll maintain workbooks with screens of SQL embedded in the VB code module. The line continuation situation gets pretty annoying then.

Space followed by underscore followed by newline = ignore. That's easier to program than a limit (plus the lame error message).

...I imagine theres a VBA developer somewhere in Redmond, reading this, cackling to themselves while they mark New Zealand on their "world map of line continuation victims"...