Jeff - Sorry, I must have been unclear, because that misses the point completely. I need to be able to programatically fire an onChange event within a script. Hence using fireEvent in the first place. This is the situation - I've got 3 select boxs. when 1st one changes - it changes values in the 2nd one when the 2nd one changes, it makes changes to the 3rd. 1, and 2 have onChange handlers to do this... so what should happen is: 1 gets clicked, on change fires, which changes 2, 2 onChange fires, which then changes 3. Now - just by fiddeling with the objects collection within the select doesn't make the 'onChange' fire - hence the need for fireEvent. Does that make more sense? > Jeff Howden wrote: > > > mark, > > ><><><><><><><><><><><><><><><><><><><><><><><><><><><><>< > > From: Mark M > > > > Had a fireEvent("onchange") happening on a select box > > with no issues. > > > > That was, until a user with IE 5.0 came along. > > > > Little did I realise that firevent didn't get > > implemented until 5.5. > > > > So! > > > > Anyone know a way I can let off a 'onChange' event > > without calling 'fireEvent'? > ><><><><><><><><><><><><><><><><><><><><><><><><><><><><>< > > short of the obvious: