Steve Werby wrote: > Others on the list made good suggestions about the database structure. The > URL you referenced reloads the whole page. I've seen other sites achieve > the same functionality by loading the elements of the second, third and > fourth select boxes into javascript arrays which and regenerate the contents > of the dropdown boxes and make them visible based on the element selected in > the parent select box. I wouldn't being doing that, based on the plain and simple reason that if the user has javascript turned off, the whole thing falls apart. With carefull <NOSCRIPT> content, it *might* be do-able, but it's one of those risks that I wouldn't be taking on a commercial site which is trying NOT to alienate customers and prevent sales. In a controlled environment (corporate intranet) I agree this style solution would be lurvly, but I wouldn't want to turn away a single user if my site relied on sales to survive. If the page that reloads is lean and fast loading, it will be the best solution to just reload and avoid problems. Justin French Creative Director Indent.com.au > This avoids a page reload, but forces the page to > load all of the possible select box elements when it's first loaded - and it > obviously requires javascript. It might be a good alternative depending on > your needs. I've found that it only makes sense when very few target users > will have javascript disabled and the potential contents of the select boxes > are less extensive than make and model detail. > > -- > Steve Werby > President, Befriend Internet Services LLC > http://www.befriend.com/ > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
