Redsoxav8r

I just ran 5 route queries as well (7:15 PM Pacific time, 24 Jul)... Got a few error messages, but still managed to get the queries through on IE7. Groundspeak, if you've fixed the problem, thanks! If it was a fluke, then I thank the vagaries of IE7 for their momentary willingness to cooperate in advance of my vacation. At any rate, I'm still going to try Firefox... [Am I allowed to say that, even though I live in NW Washington??? ]

Unfortunately, no. The page will only generate a route if it is created by the geocaching.com server, and that page as it is created by the server fails to be rendered properly by IE. Average users who use IE, which is to say the vast majority of people, are just out of luck until the people who can do something about it decide to do something about it. Based on my testing, that something amounts to changing "v=2.x" to "v=2.118" on a few pages until Google and IE start playing nice again or geocaching.com puts the map link in the body element of its HTML. Thanks, Seth. With all the other suggestions about using Firefox, I guess I'll have to give that a shot in the next day or two. I'll download it on my kids' computer, in case it kills something.

You might as well say it works for 1 out of 10 people. You'd be saying the same thing. To those who want to fix the problem and not just ignore it (and reality), this post links the same KB article mentioned above: http://forums.microsoft.com/MSDN/ShowPost....75&SiteID=1 It is document.body.scrollLeft where body is undefined that is causing the problem, at least according to my debugger, which does look like the problem in the KB article. Should body be defined? Yeah, probably, but oh well, it's not. Does it work in Firefox? Probably not. The part that I think is failing probably isn't supported by Firefox. The real problem appears to be version 2.119 of the Google Maps API existing in the header: <script src="http://maps.google.com/maps?file=api&v=2.x&key=ABQIAAAAJgGMKHyR9XoIcK-3DmCRHBRO4G3HCJ4w_V4wt439o4UygXv9mhSzv2kAJjrfphjN0BPFWxW5Tx2Ljw" type="text/javascript"></script> If I change to v=2.118, no problem, header or body. If I put the above tag in the body, no problem. But when the tag above exists in the header, up pops the error. See the discussion here: http://groups.google.com/group/Google-Maps...9af0cd79b96ec8d Ok -- interesting details, but your explanation is a bit above my ability to understand... Is there something I can do myself, as an average IE user, to get around the snafu? Or will the Groundspeak folks have to make the fix on the website?

Thanks for the fast response! Glad you folks are already on this. Looking forward to the fix.

I'm having the same problem, too. Been over a week since I could do a route query! Can't do it at work or at home, so it's not VPN, network, or specific computer-caused, as near as I can tell, since I used different computers on different networks, in and out of VPN. Also tried via IE 6 and IE7 and got the exact same error... Does anyone know what the source of the problem is, or when it will be fixed?