Telerik Reporting - Missing opertator before _Code Operand

[Giannis]

Hello,
I am testing your Report Generator and I have created a report programmatically. I am currently getting this error:
Missing opertator before _Code Operand

can you point me to the right direction? 
(I am not spelling the error message incorrectly, this is what I actually get)

[Rossen Hristov]

Hi Giannis,

From the error message it seems like a problem in an item binding expression that contains the "_Code" string.
Please review your TextBox and PictureBox items' expressions looking for the problematic string. If you cannot resolve the problem by yourself, send us your expressions so we can help.

You can find several examples of binding expressions in the sample reports that come with the default installation or you can check out the documentation where the syntax is explained in details.

 
Best wishes,
Rossen
the telerik team

Instantly find answers to your questions at the new telerik Support Center

[Giannis]

Hello,
I found out the cause of this problem. The problem occurs when setting the value for a TextBox. In this case it was like this

TextBox1.Value="=Hotel_Code";

where Hotel_Code is an alias name for a column.

When I changed the alias name to HotelCode, the problem was resolved.

[ernie racer]

same here, it seems like telerik reporting beta 2 doesn't like the underscore (xxxx_xxxx) in tablefield names.

error message:

Missing opertator before _NO operand.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Telerik.Reporting.Data.ParserException: Missing opertator before _NO operand.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

daniel

[Svetoslav]

Hi ernie racer,

We will investigate the underscore problem. Meanwhile you can try enclosing the problematic field names in square brackets: =[xxxxx_xxxxx] (same applies to the fields that contain spaces).
 

Kind regards,
Svetoslav
the telerik team

Instantly find answers to your questions at the new telerik Support Center

[Chris Ruegsegger]

This problem is still present in v1.

Chris

[Chavdar]

Hi Chris,

Thanks for the reminder. The issue is already fixed and will appear in SP1 which is due by the end of the month.


Regards,
Chavdar
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center