Google Maps Integration

[mikebrewer]

Hi all,

I'm trying to integrate google maps into my database through a WebBrowser activeX control on a form. I have the form built, I have the web browser object on the form. I then have a html file that I call to load the map into the browser control. Upon loading the map, I call a function to pass it a lat/lng so that it can place a pushpin on the map. All of this works well. The next thing I'd like to do is be able to move the pushpin to another area and pass the location back to Access to be saved in the database. However... when I move my mouse over the browser object (after loading the map), I'm getting an error pointing at a file @ google. (onion.js to be exact). What I don't know is if the problem resides with them or with me. I think it has to do with the browser support but I don't know what version of a browser access is using in order to navigate the google maps side... nor do I know how to figure this out.

Does anyone have any experience here or maybe at least know how to figure out what browser the browser object is using whenever it loads a page?

Thank you all!!

 

[Minty]

It will use an embedded version of IE and the version is set in the registry. I had to fiddle with a registry setting / version to get the map working properly in a browser object.
Unfortunately I can't seem to find the links I used to find out what to set and where... I would suggest a good google.

 

[mikebrewer]

Well... I've tried messing with the registry in about 1000 ways but regardless of how I set it, I can't get it to work. I try setting a key to force access to render the browser as a new version (https://msdn.microsoft.com/library/...f=255&MSPPError=-2147217396#browser_emulation) but whenever I go too high, I get a separate error. If I set the key to 11001, the error I get is run time error 438, object doesn't support this property or method. I assume Access doesn't know how to use IE 11 in the form (which I also think might solve the problem).

Adding this doesn't work either... (https://blogs.msdn.microsoft.com/patricka/2015/01/12/controlling-webbrowser-control-compatibility/), probably because it doesn't know to render it in the highest possible and is still reverting to IE7.

Maybe if I could force Access to use IE 11 instead of IE 7, that might do it. Unfortunately for me there, my testing hasn't allowed it to work (production is Office Pro 2010 but I tried to make this work in Access 2016 as well)