Thanks Wil. I am seeing the same thing. I can easily register the control manually and then it works fine. I also used your register program and that works fine too. But if I try the manifest method, Microsoft Visual Foxpro is never happy and it cannot find the control. For now I am calling your register program (with elevation) from my software-patch code. It's a bit awkward because there are two choices (1.1 and 2.0) but it DOES work.
I still am running into two problems that makes it hard to choose which control to use:
1. Version 1.1 gives a javascript stack overflow error when you pass an address to google maps via a URL
2. Version 2.0 leaves a large gray area on top of the Foxpro form when you open it. It appears that Foxpro has trouble with the first-time render. The control, in my app, is supposed to be on a tabbed control page (in Foxpro it's a "pageframe" control) but appears outside the pageframe with the proper offsets but from the top left of the form, NOT the top left of the pageframe page. Once you go to the page that has the control, this all fixes itself until you close and re-open the form again. I have a feeling the .ocx control does not do this but I will confirm.
I still am running into two problems that makes it hard to choose which control to use:
1. Version 1.1 gives a javascript stack overflow error when you pass an address to google maps via a URL
2. Version 2.0 leaves a large gray area on top of the Foxpro form when you open it. It appears that Foxpro has trouble with the first-time render. The control, in my app, is supposed to be on a tabbed control page (in Foxpro it's a "pageframe" control) but appears outside the pageframe with the proper offsets but from the top left of the form, NOT the top left of the pageframe page. Once you go to the page that has the control, this all fixes itself until you close and re-open the form again. I have a feeling the .ocx control does not do this but I will confirm.