![]() Alex Dybenko, provided me with the key piece of information to figure out the root cause of the problem. I also, after some reading, was lead to believe it was due to Internet Explorer’s ‘Compatibility Mode’, but after performing a few simple tests, this was quickly ruled out as the source of the problem.Īt this point I was at a loss as to what to do, so since I am an MS Access MVP, I sent an e-mail out to my fellow Access MVPs to see what others might suggest. If it were truly a Google issue, it would be generalized, which it evidentially is not! This leads me to seriously believe it has to do with some windows update that is applied to certain computers and not others. Furthermore, the error itself did not occur on every machine. I was able to confirm that using the same URL directly in a web browser (IE, FireFox, Chrome) all displayed just fine without any errors. ![]() So it was time to do some more digging.ĭuring the testing phase. That said, days, weeks, went by and the problem remained. ![]() One day, at the beginning of October 2013, my client informed me that they had recently started receiving a Scripting error (see the image below) every time the form displayed a map (Google Maps) of an address, any address.Īt first, I assumed it was a Google glitch and figured we’d give the Google team a chance to rectify whatever the issue was. I had an MS Access database which had been in place for over a year and that was working just fine.
0 Comments
Leave a Reply. |