There are several ways to use mapquest remotely, the prefered nethod is through the API calls which shouldn't change over time. The second way is using automation to fill in the form and submit, which I have done in the past. The third way is my current way of doing it which is to stuff the URL parameters with the data form the record, and doing it this way, they added a couple of parameters. The commented out line is the old code, the line below it is the new code, seems to work fine.

oIE=CREATEOBJECT("internetexplorer.application")
oIE.VISIBLE=.T.
*oIE.Navigate("HTtp://www.mapquest.com/maps/map.adp?searchtype=address&country=US&addtohistory=&searchtab=home&address="+ALLTRIM(ALLTRIM(Recd.Addr1)+' '+ALLTRIM(Recd.Addr2))+"&city="+ALLTRIM(Recd.City)+"&state="+ALLTRIM(Recd.State)+"&zipcode="+ALLTRIM(Recd.ZIP))

oIE.Navigate("http://www.mapquest.com/maps/map.adp?searchtype=address&country=US&addtohistory=&searchtab=home&formtype=address&popflag=0&latitude=&longitude=&name=&phone=&cat=&address="+ALLTRIM(ALLTRIM(Recd.Addr1)+' '+ALLTRIM(Recd.Addr2))+"&city="+ALLTRIM(Recd.City)+"&state="+ALLTRIM(Recd.State)+"&zipcode="+ALLTRIM(Recd.ZIP))


The only reason I use this method is because I didn't want to take the time to learn their API, but because of this, they can break my code occassionally.

>Bob, I changed what I thought should be changed and I still get mixed results. If an exact address is sent, the map is blank, hit F5 and it appears. Send a 'near hit' address and you get the normal prompt, select the suggested address and it appears just fine.
>
>If you can figure out what the correct syntax should be, would you mind sharing?
>
>Thanks!
>
>Dick