Hello,
I have around 29,000 values for populating a dynamic drop down control in a Html composer form. It just hangs during run time. what is the maximum limit for pulling values in drop down control?

Thanks,
Suji

This message has been edited. Last edited by: Kerry,

Really, you want a drop down box with 29,000 values? How is that usable to your users?

To answer your question, I think the limitation would be client side (your browser) (assuming your query is quick)....but loading that many values into any browser is going to be slow.

I think you need to determine a better way to do that.

Good luck.

WARNING I DON'T SUPPORT THIS IDEA :-)

Look into JQuery, they have many scripts that will allow the user to TYPE in the value and it will populate the drop down box with the corresponding results.

Again, WebFOCUS and JavaScript don't play well together, and you risk the chance of not being able to upgrade without going back to fix it.

"WebFOCUS and JavaScript don't play well together" - this I don't agree with, we're happily integrating jQuery and jQuesry UI into HTML Composer created web pages...

quote:

Originally posted by Francis Mariani:
"WebFOCUS and JavaScript don't play well together" - this I don't agree with, we're happily integrating jQuery and jQuesry UI into HTML Composer created web pages...

That is fine, you can disagree. But the fact is that in the 7.7.X documentation it says that we shouldn't be writing out own JavaScript.

quote:

Althought the HTML Composer is fully integrated with JavaScript, it is suggested that you do not create custom JavaScript that minipulates the HTML Composer generated controls, a WebFOCUS cannot support such custome JavaSCript code. Additionally, there is no guarantee that the JavaScript code will work correctly in future releases.

I just feel better with myself that when I suggest writing JavaScript to someone...that I point out that IBI doesn't support it.

That statement from the documentation does not say you cannot use JavaScript. It says that you should not manipulate the controls.

It is not that the HTML Composer does not support JavaScript... it is that it does not support JavaScript that manipulates controls that were generated by HTML Composer. This is more self-preservation than anything - so when you upgrade to a new release, and they have changed the internal code on a control for some reason, that your code is not different and your page will continue to work. JavaScript is fully supported in the events that are available in the tool. JavaScript to your heart's desire where it is allowed without consequences.