Application Crash – Large invalid query

Originally Posted 12 December 2011, 8:15 pm EST

  • Originally Posted 12 December 2011, 8:15 pm EST

    I have a recordsource that is approx 60,000 char and if something is wrong with the query instead of throwing a error message the program crashes. I tested it with any large recordsource and the same thing happens. If something is wrong with the query it crashes. Please fix it.

    PS while fixing this, it would be great if you can give the ado error message when there is a query error instead of a generic cant open recordset.
  • Reply

    Hi,
    I created sample displaying data having the same number of characters as mentioned by you.
    It did not crash on executing the wrong query statement but displays an error with proper message.
    Could you explain the exact scenario where exactly you faced the problem, sample would be better?
    Regards,
  • Reply

    Hi,
    It is still with the development team.
    Whenever I get any update on it, will let you know
    Regards,
  • Reply

    Any update on this?
  • Reply

    Its a simple fix, When can it be implemented?
  • Reply

    Here is a sample. If you open it with the report designer and try to run the first report it will crash right after the message. If you run the second report it will not. the only difference is in how long the query is.
    2012/01/test.xml
  • Reply

    Hi,
    I checked your xml file but observed that there is not table mentioned in the Select query. I wanted to know what exactly you are doing?
    Due to missing TableName, report is not able to execute the query and hence it is giving problem. To solve the same, just mention the TableName from which you want to retrieve data after every SQL statement.
    Hope you would be able to solve the problem at your end.
    Regards,
  • Reply

    You are missing the point. I know the queries aren't good. But when you run the first one with the large query the program crashes. while the second one it doesn't crash. Please fix that it shouldn't crash.
  • Reply

    Any update on this? They just need to make bigger the length of the error string before inputting data.
  • Reply

    Hello,

    I deeply regret for all the inconvenience caused but our Studio for ActiveX controls are in maintenance mode and no Bug fixes or Enhancements are being catered as of now.

    However, I have still escalated this issue again to the development team with your suggestions and have asked them if there is something which could be done in order to help you out. I will get back to you as soon as I get any information from their side regarding the same.

    Regards,
    Reema
  • Reply

    Hello,

    Here is an update :

    You need to add table name in your query then only it will work.
    Furthermore, as per the development team, large database with large recordset breaks report.

    This is a limitation of the VSPrinter control (VSReport uses VSPrinter to create the reports).
    VSPrinter runs out of memory after rendering about 5,000 pages.

    We would suggest you the following options :

    1) Migrate to the new .NET versions of C1Report.
    or,
    2) Break up your report into shorter ones.

    Regards,
    Reema
  • Reply

    Hello,

    As per the development team, this should be considered as a limitation for now.

    Regards,
    Reema
  • Reply

    Did you actually speak to a developer. He needs to just dim a bigger string it shouldn't crash on a large string error. I repeat, your answer make no sense as it seems you didn't understand this simple reproducible error. Any string longer than 100,000 that is an invalid sql statement will produce the crash of the application. If the string is less than 100,000 characters the program will give an error message that the recordset cannot be created. So it seems that they don't initialize a large enough string for the error message.
  • Reply

    Hello,

    We sincerely regret for all the delay this issue took and the inconvenience caused due to this.

    I would like to inform you that the Issue is still with the development team and we do not have any update regarding the same.

    However, I have asked the concerned team to look into this issue with high priority and will update you as soon as I get any information from their side regarding the same.

    Regards,
    Reema
  • Reply

    Hello,

    I am really sorry for all the inconvenience caused but there is still no update on this one from the development team.

    I have pinged them again and have asked for an update on this.
    I will get back to you as soon as I get to hear from them.

    Once again, I apologize for all the delay this issue has taken.

    Regards,
    Reema
  • Marked as Answer

    Reply

    Hello,

    Please accept my sincere apologies for the delayed response.

    As informed earlier, our ActiveX Controls are in maintenance mode and we no longer provide any bug fixes or enhancements for the same.

    This being said, we can still look into the matter and if a reasonable set of customers demand for a bug fix we can try to fix it or maybe suggest a workaround for the same, if it exists.

    With regards to your query however, there does not exist a workaround as such and we deeply regret all the inconvenience caused due to this.

    Regards,
    Reema
  • Reply

    So you aren't fixing bugs anymore in the activex version (Should we discontinue paying annual support?).
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels