I would say it depends on your users connection
speed. If your users have fast connections
and your queries are tuned, it's probably
easier to make the round trips. I've used
the javascript approach with a slightly
smaller dataset and it works, but there are
some differences in how IE/Netscape interpret
javascript.
If your users have slower connections, I would
definately pursue the javascript approach;
it will take a little longer to load the
first page, but you save the round trips.
-Chip
"Dennis Hallman" <[EMAIL PROTECTED]> wrote:
>
>I have a page with 3 combo boxes and a list box. The combo boxes are dependent
>on each other. i.e So when combo box A changes it affects B and C,
>And when B changes it affects C.
>
>The design issue is whether to make a trip to the server each time a combo box
>is changed or to create a JavaScript array in ND on the OnBforeHTMLOutput Event.
>
>Combo Box A will have about 6 entries
>Combo Box B has 60 entries 10/each entry in A
>Combo Box C has 700 entries 12-15/each entry in B.
>
>Which avenue would you pursue or does anyone have any other possible design
>soultion.
>
>Thanks
>Dennis
>
_________________________________________________________________________
To unsubscribe from this mailing list please send an email to:
[EMAIL PROTECTED]
Please remember to use the same email address you subscribed with.
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
