options.length is null or not an object.

[Lee Firth]

I have a Dynamic Dropdown on a page which seems to work fine if I just go directly to the page in the browser. This page is part of a number of forms that update a record, when I arive at the page as part of the update process (it is form 3 or 3 forms) a parameter is passed as part of the querystring to open the same record again. If I try to use the Dynamic dropdown now I get an error message:

"options.length is null or not an object"

If I remove the parameter from the querystring and refresh the page, the dynamic dropdown works OK again.

OK I've done a little more troubleshooting. It has nothing to do with the querystring. In the previous page I edited the Update Record SB and deselected "Pass original querystring" and it still happens. Might be something to do with the fact that we arive at this page by means of a redirect?

[Eric Mittman]

The only reason this page should change depending on how you get to it would be if you were filtering any of the recordsets on the page with any query string or other variables from a form post or something like that. If the data on the page is the same then the page should behave the same regardless of how you navigate to it. Please do some testing with this page and redirecting or linking to it to see if you can narrow down when this issue occurs. If it only happens under a curtain sequence then that would point to the data on the page changing as the source of the issue. Also do you have a link where this can be seen in some fashion?

[Lee Firth]

Unfortunately this website is part of an intranet and I can not give you access to it. I have however recorded a screen capture video which demonstrates the problem I am having:

http://www.firthwebworks.com.au/recording.wmv (http://www.firthwebworks.com.au/recording.wmv)

[Eric Mittman]

Thanks for the video. I have opened a ticket for you on this issue so we can exchange some files. Please login to the site and visit you support history to update the ticket. I think the problem is likely posted info on the last page but we will be able to see this better when I test it.

[Eric Mittman]

The problem here was the name of your second select list, it was named referrer. This is also an internal value for the webpage that will hold the referring page address. Because of this that name should not be used.

The fix is to use a different name for the form element. If it is updated in all locations that it appears the problem should go away.

[Lee Firth]

Thank you for your help on this issue Eric. I was scratching my head for hours trying to work out the problem.

[Eric Mittman]

You are welcome, I too was scratching my head on this one. I have not seen anything like it before. I was glad that I found the problem and hopefully the knowledge learned will help me in the future if I encounter anything like this again. I hope you too have learned a little from this experience, it was an odd issue indeed.