GetListItems issue

I am using the GetListItems function to retrieve an ID (not the internal id, just a text field) from a list where a lookup column exists. I want to automatically populate a field on my form with that value and it works great. This is the isue.
This column contains over 20 items so in IE it renders differently than in FireFox where I'm seeing no issues. I have one other lookup column in my list that has over 20 items as well. The column I'm running the SPServices script on is defined
as having an id="customddl", my other drop down list is the default code. When this second drop down list is changed, it's callin my SPServices function when it should not, and thus clears out my populated field.

These are the 3 table rows returned in IE at the top of my form that are doing all this. I've cleaned up a bunch of the choices and hopefully formatted it well enough to make it readable. The first and third rows are the DDls with the second
being the one I'm trying to automatically set.

I moved the ID to the formfield code but that didn't help. This is the SPD code. It does select the right cell initially and sets the value, I just don't understand why it's occurring for the other drop down.

If I change the selector to $("input[title='Lab']").change(function(), it still removes the value from the Lab ID text box. Could it be possible the onChange(HandleChange) function is causing an issue in the html output? It is truely baffling
to me. For once Firefox is playing nice and not IE :-(

One option would be to hard code this as a select element and use SPServices to fill it. This way it does not matter if there are more than 20 items or not. Not sure exactly what you are doing but I have done this and it seems to work well.

The select may work for one of them by not the other, it has nearly 300 entries. I'm just not understanding why this works in Firefox and not IE. I've tried a variety of selectors to ensure it's isolating the proper input field, but the second
ddl is always triggering the function.

Keep in mind, Eric, that SharePoint renders the control very differently in IE than in Firefox. In Firefox the 20+ dropdowns are still plain old selects; in IE they are rendered as a hybrid input/select combination with a bunch of script behind it. Your
script needs to manage the two differently, as I showed you in my SPDisplayRelatedInfo function.

Also, View Source shows you the page as it is sent to the browser, not as it currently is at any point in time. For that, you need to use the Developer Tools in IE8 or Firebug.

Yup, I meant the function inside SPServices. If you look at it, you'll see how I handle the difference between 'simple' and 'complex' dropdowns, which is what you need to do if you want things to work in IE and Firefox. M.

I'm not sure if I'm understanding the issue correctly, but as Marc mentioned there is some script behind the crazy IE combo control. Your best bet when attaching onChange handlers to these hybrid controls is to use the hidden input field. Check out
this post from Boris Gomiunik for details.

You'll still have to handle the lookup fields differently for FireFox/Safari/etc. but it's a lot easier since you can use $("select[title='fieldname']) to select a standard Select control.