Tuesday, November 30, 2010

Verifying SQL Inserts

There is a new option you can turn on or off in the Global Personalization screen that will "Verify SQL Insert when Adding Records". If this option is turned on, the program will check to make sure the new record has been added successfully before continuing. If the Add action fails, you are left in edit mode and either have to Save again or Cancel. An "ERR_INSERT" text message is created in the main ZPSQL folder as well. This new option should only be used for troubleshooting as it does cause an extra SQL call to the internet each time you add a record to an application database. All of the application databases have been updated to support this new option. The downloads are available now.

Tuesday, November 23, 2010

Occupant Mismatches Web Page

This post is a follow-up to my November 7th post. I decided to add another page to the Staff web site Contact File maintenance section. This one shows any Contact records that are listed as the "Occupant" of a property but whose Contact street address does not match the street address of the property they occupy. In the previous post I advocated using an Advanced Filter to review these same records. Now there is a web page that does it for you.

Thursday, November 18, 2010

Removing Duplicate Contact File Records

I just added two cool new options to the Staff web site that can help eliminated wasteful duplicate records in the Contact File database. You can access the new pages from the Contact Search option and then going to the Contact Maintenance page. The new options attempt to find existing duplicate records in the Contact File database by showing the most frequently repeated street addresses and the most frequently repeated names. Using either of these lists as a starting point you can select duplicate records and merge them together so that only one Contact File record remains but the links are preserved. To better explain how to use these new pages and the Contact File Upkeep option in the Window interface I've also added a new tutorial "Contact File Maintenance In ZonePro SQL" to our web site. It is a riveting piece of non-fiction that I highly recommend adding to your reading list.

Wednesday, November 17, 2010

Web Site Linking Follow-Up

To expand on my last post, we've added special pages to the Staff web site that make it easy to link to specific property records by passing either a parcel number or Property ID. An example parcel pass would look like this: www.zpdemo.zpuser.com/work/linkparcel.aspx?parcel=500-12-003. We also added an extra parameter that lets you link specifically to our mapping page, our driving directions page, or the page that tags neighbors with a certain radius. An example link for directions would be: www.zpdemo.zpuser.com/work/linkparcel.aspx?parcel=500-12-003&link=directions. A new tutorial is available on our web site called "How To Link To ZonePro SQL Web Sites" that explains this option further.

Friday, November 12, 2010

Linking to Web Sites Via Parcel Number

Had an interesting talk with a GIS company yesterday. They wanted our mutual customer to be able to display ZonePro data for a particular property record from within their GIS interface. The solution we agreed on was that the GIS program would pass a parcel number to the Staff web site for that customer which in turn would bring up the matching ZonePro Property web page in an inset window of the GIS page. This kind of linking is very easy to with our web interface for ZP SQL. Basically we just created a special web page that captures the passed parcel number and then launches the appropriate property record page. This same technique can be used by other communities and third-party tools that would benefit from a link to ZonePro data.

Sunday, November 7, 2010

Checking Occupant Integrity

A recent exchange with a customer sparked an idea for an interesting report. Theoretically any Contact File name that has a relationship of "OCCUPANT" should have the same address listed in both their Contact File record and the property that they are the occupant of. A quick way to find records that break that rule is to run the "Basic" report in the Contact File Report Screen and use an Advanced Filter like this:

CFTYPE = "OCCUPANT" AND ST_NR <> P_ST_NR
This filter just checks the street numbers listed in the Contact record and the Property record, but that should be enough. Any Contact records that show up in this list probably need a correction, either to their Relationship type or to their address.