Tourbleshooting errors

[jay@bplogix.com]

What is the best approach to troubleshooting errors when we get runtime errors like "Error #2032"? After spending time editing a report, it is difficult to find out what the problem is. Typically it is a simple variable error or a typo anywhere from the Group, to a datasource, to a field in a datasource. Unfortuntaely it is VERY easy to create runtime errors in reports simply be editing a report.

How do we know "where" the error actually is? The only I can find is to literally delete objects one by one in the report until the error dissappears. But there has to be a better way

thanks

[HighAley]

Hello.

It's a Flex error. Do you have any particular problem with it?

Thank you.

[jay@bplogix.com]

I dont know what "Flex error" means? I guess the problem I am running into is that if I edit a report, and then run it, it sometimes just returns Error #2032 if I made any type of configuration error in the report (any kind of typo). How are users supposed to troubleshoot errors like this? For example, edit a calculated column, and have a typo. Now try to run the report. I just get Error #2032. But how do I know where the problem is? I could have been editing dozens of fields.

thx

[HighAley]

Hello.

Sorry, we need a little more time to prepare an answer for you.

Thank you.

[HighAley]

Hello.

We have put this issue in our to-do list. Look for our updates.

Thank you.

[jay@bplogix.com]

Is there at least a way to view the CS generated code? That way a user can search thru the code for ideas of what is causing the failures. It seems that there is a lot of ways to cause the error ... and without some basic hints as to where the error is, it is kind of like a compiler just saying "compile error" without telling the user where or why.

thx

[HighAley]

Hello.

You can show the code of the report by setting next option:

Code: Select all

StiWebDesignerOptions.Toolbar.ShowCodeTab = true;

Thank you.

[jay@bplogix.com]

Thx. That works pretty well. I remember in previous builds it would show this by default, and would actually navigate in the source code to where the error was. Has this logic changed?

[HighAley]

Hello.

Thx. That works pretty well. I remember in previous builds it would show this by default, and would actually navigate in the source code to where the error was. Has this logic changed?

No, the Winforms Designer has such behaviour but not Designer.Web.

Thank you.