28 Feb 04 -- they outsourced petwhere for yet more delays.  we can no long offer support for petwhere; as we are overburdened with support requests, and aspca no longer returns emails or phone calls regarding obtaining the source code.  

3 Feb 04

• Here is the offical word I have received from the ASCPCA, I quote:

The ASPCA has suspended development of PetWhere 3.0 but the help line is still open and operating. We are in the process of transitioning development back to Bosack-Kruger who is exploring other alternatives at this time.

26 Jan 04

• New version? "Hurry up and wait" is close, but I think "Give it up" is more appropriate.

• I found out the other day & have confirmed it. The development staff for the new petwhere was let go. The helpdesk there was let go.  I could not find out what is going on. 
• I have again asked for thesource code for 2.6 so I can support it better...
• My contact there (David Flagger) has left (2 months ago I hear). He used to manage the project.
• Basically, I got the impression that the project is dead again; and  will be outsourced AGAIN; which means likely another delay on the order of years probably. That's just my hunch; it is not based on any factual evidence.
•  I would start looking at alternatives to petwhere.

Update 19 Nov 03: 

• They are still working on 3.0 -- no news on a release date.

• The conversion mentioned the other day is a "stop gap" measure for helping with the troubling GPF's and other problems -- especially on new computers.  They are not even sure if they'll do it.

• The converted program will have no new functionality.

• There is no release date for this converted program.

Update 17 Nov 03: Petwhere news at jAssing.com

• Just got an email from ASPCA -- news is: They're finally going to just "convert" the FoxPro (FPW) code to VFP (that will make it faster, prettier and more reliable on faster computers -but likely add little to no new functionality).

• Custom report engine was scrapped --after talking to ASPCA and my lawyers, it would violate the Foundation's (c) on the program. Sorry.

• I offered my consulting services to ASPCA to help with the conversion. This type of work is my specialty.

• I have no new information on the 3.0 release.

• I'll be posting another ZipCode update w/in the next month or so.

Update 06 Mar 03: PetWhere news at jAssing.com

• I released a patch to allow you to change breeds -- be careful; this may invalidate your data if you don't edit the table correctly!

• Custom Report engine is in the works (for 2.6) I'm sorry to say; I just don't have the time to complete this as of yet.  I've been swamped with paying clients, so this has had to take a back seat.

• email list on line -- to join, send an email to listserv@jassing.com with the body "Subscribe PetWhere" (w/o quotes)-- if you have problems, contact support@jassing.com. This list will be for letting you know about updates -- and for user-to-user assistance with PetWhere issues.

Update 17 Jan 03: PetWhere news at jAssing.com

• 2.6 code cannot be released, the ASPCA doesn't even have it; and the Foundation will not be releasing it.  So if your shelter cannot get new hardware required for the new version, I'm afraid your stuck with the existing 2.6.

• Custom Report engine is in the works (for 2.6) -- this version will be free & more robust and (hopefully) easier to use than what the Foundation was recommending (FoxFire).  I hope to have this done by the end of January.

• 3.0 development appears to be near beta -- I've been told I'll be able to get a beta copy so I can continue to help the shelters that need my assistance.

• email list on line -- to join, send an email to listserv@jassing.com with the body "Subscribe PetWhere" (w/o quotes)-- if you have problems, contact support@jassing.com. This list will be for letting you know about updates -- and for user-to-user assistance with PetWhere issues.

Update 4 Jan 03: Updated PetWhere Backup Utility Posted.

• Thanks for the positive feedback, here is the promised "Service" version.  Let us know if you have any problems. (support@jassing.com -- Also; ask to be added to the "update" list if you want to know when an update is available.
• Per request, this version now enables you to backup the CDX file so you do not have to run FPR on restore. (I'm pretty certain I have everything that can be configured, configurable thru the ini file)
• An email list has been started, if you're interested, join up by sending an email to our automated server: listserv@jassing.com with the BODY "Subscribe PetWhere" (no quotes) It can't understand HTML messages, so please use plain text, or send an email to a real person at support@jassing.com -- This list will be used for two purposes: 1) To allow users of PetWhere to talk among themselves regarding PetWhere issues; and 2) To be notified if & when new PetWhere utilities (by jassing.com) are ready (Such as the backup utility).

Update 28 Dec 02: PetWhere Backup Utility Posted.

• I have posted a utility for PetWhere to automatically backup your data files twice daily, and automatically remove those zip files after 30 days (both items are configurable).  If you would like it; you may download it here.
• To the best of my knowledge, 2.6 development is "Dead".
• There is still no timeline on 3.0 release. 

Update Nov 02:

• I provided a patch for a shelter to change the "internal" Display name for a drug.  They were told by ASPCA that it "couldn't be changed".  
  PetWhere's "internal tables" were made "internal" so that some standards across shelters could be achieved.  However, they were also designed so that it could be changed easily.
  This patch does nothing to remove that "standard" as it changes the name of the drug that is displayed only.  
  If you would like a patch similar to this; let me know.
  Please note: I cannot ADD any drugs, that would require the source.  Also; YOU would be the person running the patch, which will modify the executable, which may be a violation of copyright laws.

Update Mid 2002

• Bosack-Kruger has nothing to do with PetWhere anymore, except fund it.
• support@petnet.net (or ANY petnet.net email) will be lost, that mail server is offline.

I have verified that Bosack-Kruger has terminated the project (in house) and is outsourcing it. For now, it appears as if support is limited.  

Update 28 Aug 01: Their web site was down again for about a week. 

• I hear Glenn at Bosack-Kruger has not been "over burdened"  but they have moved the Redmond, WA office recently.  The suggestion was to "keep trying" if you are calling or emailing.
• I've been receiving more than my usual # of emails  with questions regarding the status. I do not know more than I post here.  But PLEASE feel free to contact me if you have questions/concerns.
• Feel free to  contact David Flagler at ASPCA he is the "coordinator" and person "in charge" for PetWhere now.
• David reports: "We have not received a time line from our developers, but we are now looking at Spring or Summer of 2002 for the release of 3.0."  It is up to you how to interpret that.
• The relation between the Foundation & ASPCA is simple: Glenn at the Foundation (in Redmond) is holding down 2.6 support; ASPCA is doing 3.0 development in Illinois.  When 3.0 is release, ASPCA will take full control over PetWhere.

UPDATE 16 May 01:  David R Flagler from the ASPCA has been in contact with me to let me know that he was put in charge of the PetWhere product 1 week ago.  I have not received any timeline on the development or deployment of 3.0.  Feel free to contact me with concerns and I will pass it on.

(c)