I could reload the page with plain asp but I was hoping to avoid another trip to the server.
With AJAX you aren't reloading the page though. You're making a trip to the server to pull a very small amount of information, and then using javascript to make the appropriate changes.
As an alternative, you could just load all possibilities for your radio buttons when the page initially loads, and then save those possibilities into client side arrays. Then, when the radio button is clicked, load the <select> with the information from the array. For your scenario this probably wouldn't be a bad solution because you only have 2 radio buttons. This makes a small subset of possiblities for your <select> box.
But... imagine if you had 100 radio buttons. That means that you'd have to load in 100 different possible arrays of options for the <select> box. That's a lot of unnecessary strain on the server, and bandwidth wasted. In this instance, it's much more desirable to pull the subset of data when they click on each radio button. It's likely that they'll only be clicking a radio button once or twice on the page, so that means you'd be pulling 2 or 3 sets of possible arrays instead of all 100.
You're free to design this however you'd like, but from a professional standpoint I think it would be beneficial for you to use AJAX for this. Even more so if you've never used it before because that will give you another tool under your belt. AJAX can be used for loads of things, but this is a very simple example that could help you to get your feet wet.
-kaht
Lisa, if you don't like your job you don't strike. You just go in every day and do it really half-assed. That's the American way. - Homer Simpson
[small]<P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P>
<.</B>[/small]