SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


error [BC30494] Line is too long


error [BC30494] Line is too long

Author
Message
Stefan K
Stefan K
SSC-Enthusiastic
SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)

Group: General Forum Members
Points: 158 Visits: 44

Hi,
I have a problem with a report in SSRS 2005. I tried to add some custom code to a report.
The code is absolutely simple and correct.
But when trying to show the report the debugger shows the following error message:
error [BC30494] Line is too long.

When I remove the code the report works again.

The code is about 12 words and could not be the problem.

Could anyone help please?

Best regards,
Stefan




Kindest Regards,

SK
vijay_rb
vijay_rb
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 4
Hi,

This has to do with the table regions in your report rdl.
SSRS in the backend converts all table regions to a vb code.
this generated vb code has a size limitation of 64k.

It occurs when you have wide table regions.
which actually contain n*m textboxes and which have to get converted to vb code as textboxes.

There can be two ways to try and remove this error:
either reduce the no of columns in the wide table.
if business demands the columns, then we could try to split the tables into two and make it look like one.
Since the vb code generated is per table region, this reduces the size of each vb code per table.

Another simpler thing to try before splitting the tables,
is to try and renaming all textboxes, controls in the table to a smaller name.
try something like t1, t2, t3 ...
this would also reduce the size of the vb code to some extent
plane4don
plane4don
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 0
Hi there.
Is this just an issue with SSRS 2005? We are getting ready to upgrade and we are having this issue in a few of our reports. I just wonder if I need to break apart the tables, or will this not be an issue in SQL Server Reporting Services 2008R2?

Thank you.
P
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search