This topic is locked

May 18, 2012. PHPRunner 6.1/ASPRunnerPro 7.1 maintenance release

5/18/2012 11:54:43 PM
ASPRunner/PHPRunner change log

May 18, 2012. PHPRunner 6.1/ASPRunnerPro 7.1 maintenance release

build 11825
In this update:

  • fixed issue with tab/section renaming (tab content being preserved after name change)
  • Intellisense made optional (Project->Settings->Enable Autocomplete)
  • Google Maps geocoding update. If you use Google Maps in your applications read instructions below.
    In the latest update we have switched to Google Maps API v3. Besides the updated version of API Google has also changed their terms making use of Google Maps a bit more prohibitive. They put limits on number of geocoding requests you can send per day and also limited requests rate. For example, if you have a page with 20 records and need to display a map for each record only about 10 maps will be displayed properly. To overcome those limits you need to open a fairly expensive Premier account with Google that costs $10,000 per year.
    The solution is to use latitude/longitude pairs instead of addresses for mapping purposes. The main question is how to convert existing addresses to lat/long pairs? We have added a small utility to PHPRunner/ASPRunnerPro that will do all the job for you. Here are instructions.

  1. Proceed to the table that stores addresses and add to new fields to that table. Fields need to be able to store floating point numbers. In MySQL use Decimal(10,6) or Double. In MS Access use Number with 'Field size' Double.
  2. Proceed to the field that is setup as 'Map'. Make sure that Address and Latitude/Longitude fields are selected.
  3. Proceed to BeforeProcess event of the table in question and add the following code there



asp_include "geocoding.asp"

4. Build your application and proceed to the list page in question. Add a special ?geocoding=1 parameter to the URL i.e.



If you did everything right you going to see a progress bar that shows how many addresses need to be processed:

If your database changes frequently you need to open this URL occasionally i.e once a week. It will only update those records where lat/long pair is empty which means it's safe to run this script as often as you want. Unfortunately you cannot run via cron job - Google Maps API is Javascript based and needs to run in the browser.