As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Hi, I have a maintain application where i have only one form with a Read/Write Grid in it which is used to update rows in database.When i am trying to update any row, the browser throws a alert message "Stack Overflow at line:" where 'some no'. is different for different rows.But after that the rows are getting updated properly. i.e, all the functions are working fine but this alert is coming in between.Can anyone suggest me the way to avoid this alert? I am using Internet Explorer. Let me know if further detail is required.
Thanks in advance.This message has been edited. Last edited by: Kerry,
Please check for any of these conditions. Any of them could cause the stack overflow error.
1) Too many nested IF - THEN - ELSE statements. I think there was a limit of 30. More than that could case the error.
2) Many ON NEXT / ON NONEXT statements. If you are looping through your database one record at a time, and checking if there are anymore, you definitly hit this limit. The way around that is to check for FocFetch. If FocFetch=0 then there are more records. If FocFetch=1, then no more records.
3) Too Many lines or objects on Winforms. If this is a VERY large maintain, or there are hundreds of items on your form, you could hit a tokens limit, but I think that's a different error message.
If none apply, send me a repro and I will take a look.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003