Even though you can test changes you make to the detection script as you develop it even without an activation (except with array configurations, as noted earlier), you do need to close the browser on the client and re-open it to test again. This type of trial-and-error can be frustrating, but there are other things you can do. The easiest way to keep an eye on things during development is by the use of the MSGBOX
command to output harvested data. Simply embedding these into your code will allow you to observe the response of each function as you step through the script, plus the information that was collected. For example, consider the following screenshot:
Using so many of those may seem like over-kill, but it's exactly the kind of methodology that will help you isolate those little annoying typos that could take hours to find otherwise. Did you notice the bug above? Line 4 names the variable incorrectly (stsVuzepath instead of strVuzepath...