DONATION Bug in 3.33b Beta Fixed

December 22nd, 2010

For those of you who downloaded the beta version of DONATION 3.33b in response to an earlier post, I have to tell you that a slightly nasty bug was just caught in it. If you try to use the Email/Print button on a statement report or receipt, you get an error message at the end.

This bug has been fixed by version 3.33c, which I uploaded to the regular web site (not just as a beta version) yesterday. You can upgrade to it with Help -> Check for Updates.

Because of the impending holiday season, I’m not planning on sending an email out to all users about this version until early in January. For those of you for whom this time of year is special, best wishes for the Christmas season!

DONATION – question about saving receipts

December 17th, 2010

Sorry to bug you again so soon, but I suddenly had a thought about a somewhat signficant change that I wanted to get people’s opinions on.

Currently, if you create a receipt (or receipts) using Receipt menu options other than Current Donor Sample, and then close the receipt-viewing window without printing them, saving them to PDF or sending them by email, a question pops up. It asks whether you want to save the receipts back to the database anyways.

I find what happens a lot is that people answer Yes to this, when they should have answered No. Then when they go to run the receipts later (perhaps at the year end), they find out that some donations have already been receipted, even though the receipts weren’t sent to the donors, and those donations thus aren’t included on the new receipts. The solution is usually to delete all of the receipts with Receipt -> Delete Range, and then recreate them. But this leads to a lot of support calls and emails!

What I’m wondering is, maybe I should just remove the option to save the unprinted receipts to the database. So if you have only viewed them, and close the window, they are gone. It is just a preview, in essence. (There would be a message explaining that, but no option about it.) That would eliminate that support headache for me, and that problem for those users who have that problem.

I really can’t think of a situation in which I would want the receipts to be saved even though I hadn’t printed (or PDF’d or emailed) them. Can any of you? You can always recreate them with the same Receipt menu option you just used, of course.

Another slightly related change that I already made yesterday was, if someone uses Receipt -> All Donors and it’s before the year end, to put up a message saying that that menu option is usually only used after the year end, and confirming that the user wants to do that.

Any thoughts? Thanks.

DONATION Beta 3.33b; Draft new Website

December 15th, 2010

Hello DONATION beta testers and advisors.

First of all, I’m working on a significant revision to the web site. It’s not all done, but you can see the progress at www.software4nonprofits.com/new. The significant changes are a new introductory splash page, replacing the top bar and side bar menus with a top-bar drop-down menu on the rest of the pages, and a new quick links section at the bottom of each page.

Any comments?

Next, I’ve added a few cool features since version 3.33 that I last wrote to you about, and released a beta version as 3.33b Beta3. As always, you can download and try it out from www.software4nonprofits.com/pretest.htm. Here’s what’s in it:

  • You can now double-click on backup files (e.g. DONATION4.DB.GBK) or emailed backup files (e.g. DONATION4.DB.S4B), and if DONATION isn’t open, DONATION will start and you will be prompted to restore that backup.
  • Completely replaced the features of the Save As button on the report-viewing window. It now brings up a new window with clearer choices, and some new options like displaying your saved file in an appropriate program (such as Excel) after saving it, and sending it by email to someone.
  • Made a small improvement in the installation programs, when you are upgrading an existing installation. Previously, if you had manually updated your desktop icon for DONATION to have a shortcut key to start it, whenever you upgraded that shortcut key would get lost. Now it is retained.
  • Added information in the Network Versions of DONATION help page, explaining how they can also be used over the Internet (e.g. with the Network Server version of DONATION on a computer in your office, and the Network Client version at home).
  • Added a new help page on Multiple User Options for DONATION, listing three options: multiple Standalone or Lite installs (copying the database around), Network Versions, or remote access.

If you have any comments on those changes, or testing results (positive or negative) I’d love hear them too. I’m especially pleased about the first two points above.

Thanks.

Beta Test DONATION Version 3.33

December 2nd, 2010

I am going to be releasing a fairly minor new version to the web site shortly, though because it is so minor I don’t plan to send an email to all users about it. (It will still be available via Help -> Check for Updates, of course.)

If those of you who can spare a few minutes could give it a quick test, to make sure I haven’t missed anything, it would be much appreciated (and of course a service to the many other users of DONATION, if you help save them from a bug!).

As always, you get this new version from www.software4nonprofits.com/pretest.htm. Here are the changes and fixes in it:

  • Moved the One Date reports, previously under Reports -> Donation, to a new sub-menu, Reports -> One Date Donation. (This was discussed in my previous blog post.)
  • Added two new reports under Reports -> One Date Donation: Details and Summary, and Details with Member/Envelope # and Summary. Each combine the respective Details report with the summary by category part of the Summary report, on one page if they both fit. (The three previously-existing individual Details or Summary reports are also all still available.)
  • Added a new report, Reports -> Donation -> All Donations -> Sort by Amount.
  • Fixed a bug in the Standalone version full installation program (doninst.exe) that in very unusual circumstances would give an incorrect error message that you were trying to upgrade from a version prior to version 2.30, and not let you continue the installation.
  • Fixed a bug where you are backing up to a USB memory key that has insufficient free disk space to hold the backup, and it says the backup was successful, but in fact it wasn’t. (Fortunately given the capacity of USB memory keys, and the usually very small size of DONATION database backups, this would have been a very unusual occurrence!)

Thank you.

Change DONATION’s One Date Report Menu?

November 22nd, 2010

I have just added two more reports to the Reports -> Donation menu, One Date Details and Summary, and One Date Details and Summary with Member/Env. #, which combine the One Date Details reports with the Summary by Category part of the One Date Summary report. That will allow some users to print only one report, who previously printed two, to confirm one date’s donations.

However, that brings the number of options on the Reports -> Donation menu to 16, which is a lot. The more options on a menu, the harder it is to find things. So, I’m thinking of moving the now 5 different One Date reports (3 if you have the Member/Envelope # field turned off, so you don’t see the related reports) to a new submenu.

There are two options. The first is to have it be a submenu off of Reports -> Donation, e.g. Reports -> Donation -> One Date, so the first such report would be Reports -> Donation -> One Date -> Details, and so on. The advantage of that (over the next option I will present) is that it will be easier to find for existing users. The disadvantage is that it’s another mouse click or keystroke to select those reports, which especially for churches are among the most commonly used reports. Also, for those entering the program with the Limited User password, who currently have only those One Date reports available under the Reports -> Donation menu, it will look strange to have to go down an extra level to get to those reports.

The second option is to have a new submenu under Reports, namely (say) Reports -> One Date, or perhaps Reports -> One Date Donation, with the 5 specific reports under that. The advantage of that is that it keeps it to the same number of mouse clicks or keystrokes to get to those reports as it was before. The disadvantage is existing users will have to figure out where to find those reports now. (At least, those who don’t read and understand my notes about what’s in the new version that I send out with the release emails!)

Or of course, I could just leave things alone, and let people suffer with a long list of 16 reports on that Reports -> Donation menu.

What do you all think I should do about this? Please Comment on this blog post to let me know. Thank you.

Running the Network version of DONATION over the Internet

October 26th, 2010

I have just proved to myself what I suspected for some time, which is that it’s possible to run the Network Version of DONATION over the Internet, so that you can access it from multiple locations. I’ve written a Support Forum article on it, and I’d be very much interested in any comments you have on this idea. To some extent, I feel that it addresses part of why some users would prefer web-based software, namely the fact that you can access it from multiple places.

Here is the entire post from the Support Forum:


Hello DONATION users. This is Dan Cooperstock, the author of DONATION, with what I hope will be some helpful information.

Under limited circumstances, it is possible to run a Network Version of DONATION over the Internet, rather than in the usual setup of having it installed only on several computers on a local area network within your office. (I.e. users can access the same database installed in your office, from their homes.) However, you will almost certainly need assistance from a network support person to get this working. (I cannot talk a person that isn’t familiar with networking issues and router configurations through this!)

The first requirement to do this is that you have a server (or non-server) in your office, which can be accessed via a static IP address and/or an Internet-accessible hostname, on which you can install the Network Server version of DONATION. You will have to leave that computer always running (though DONATION doesn’t have to be running on it) so that the other computers you want to access DONATION on over the Internet can access it.

Technically, the computer running the Network Server version of DONATION could even be a home computer, but then you would have to leave it on at all reasonable hours when someone else might want to access the database. And also, Internet speeds on home computers are often slower than those in your office.

If the computer you want to run the Network Server version of DONATION on does not have a static IP address or Internet-accessible hostname, you can use free or inexpensive services such as www.dyndns.org or www.no-ip.com to set one up.

Next, as usual with the Network version of DONATION, you need to follow the instructions in the Help topic on “Network Versions” to open up your firewall on that computer to allow incoming accesses on port 3050.

Assuming that computer is behind a router, you need to use the router’s user interface (usually web-based) to allow for port forwarding of incoming requests on port 3050 to that computer running the Network Server version of DONATION. Some router software may call that something like enabling application support.

Once that is all set up, install the Network Client version of DONATION on whichever other computers you want to install it on, as long as they have high-speed Internet access. Presumably this will be some of your users’ home computers. When that installation program prompts for the hostname for the network server computer, give it the correct hostname, as discussed above. (You can alternatively give it the IP address, but only if that is a true static IP address.) If everything has been set up correctly, those remote instances of DONATION should then work, accessing the database on the computer in your office that is running the Network Server version of DONATION.

Please note that because the data access is over the Internet, even with a high-speed Internet connection this will run significantly slower than the normal Standalone version, or even the Network Client version installed on another computer in your office.

In my testing, I was not able to also have additional Network Client versions of DONATION within my own local area network work successfully accessing the Network Server version’s computer via its external hostname (which I established via www.no-ip.org). I had to set it to the internal hostname of the Network Server version’s computer, and then it worked fine.

If you are going to do this, you absolutely must put a password on your database, via the Database -> Change Password -> Program Entry Password menu option, and optionally also set the other passwords there if you use them. That is because anybody that knows the hostname of your Network Server version’s computer could install the Network Client version of DONATION on their computer and access and modify your DONATION data, as long as they could get past any password prompt it gave them.

Also of course if you are going to do this, you need to purchase a license for the Network Version of DONATION.

Beta Test new version 3.32

October 23rd, 2010

Hello DONATION beta testers.  I have just uploaded version 3.32 Beta1 to the usual page, http://www.software4nonprofits.com/pretest.htm, for your testing pleasure.

The changes for this version include only a few tiny new features, and are mostly bug fixes

However, one of those bug fixes involved changing the database layout a bit, so when you first start the new version, there will be a quick invisible conversion step. As a result, (a) I would recommend that you make a database backup before trying this version, and  (b) it’s really quite imporant that a few people at least test it before I release it to all users. (That’s because if there was a problem with that conversion, which I seriously doubt, but is of course possible, I wouldn’t want to spring it on everyone at once!) And of course, if any of you do encounter a problem, I will be available to fix it ASAP. No worries!

The following is a list of all of the changes in this version.

  • Added a menu option, Help -> Move DONATION to Another Computer, which takes you to the help topic Move the Program from One Computer to Another. (This is the most common technical support question I receive!)
  • If you have multiple databases (created with the Database -> Switch Databases menu option), after you create any backup it will remind you that you need to back up your other database(s) independently, by switching to them and backing them up. (A backup only backups up the database you are currently in.)
  • In the Help page on Using a Logo and Signature Bitmap on your Receipts, added a section on how to get inexpensive help editing your logo and signature bitmaps, if you are not able to do so yourself.
  • Fixed a bug in the Database -> Import Donors menu option, where if the file to be imported contains quoted fields that are the maximum field length (e.g. 30-character First or Last Name fields), the names would be truncated because the quotes were being counted as part of the length.
  • Fixed issues in both the Database -> Import Donors menu option and the Database -> Import Donations menu option, where if you had saved the file to be imported from Excel, and Excel was still open, those windows could fail to open the import file.
  • Fixed a bug where if the First or Last Name fields were filled in to their maximum length (30), and contained accented characters, the Donor List would stop loading correctly on subsequent runs of DONATION, with an error message.
  • Fixed something more fully, that was supposed to be fixed in version 3.31 but only sometimes worked: In some versions of Windows, some PDF printing of reports and built-in receipts may not work unless you run DONATION as an Administrator. If a PDF print fails, you may be given a message to exit DONATION and re-run it as an Administrator, to resolve this problem.
  • Fixed a bug when using the Email/Print button in receipts, where it could give you an erroneous error message that it couldn’t create the Report.pdf file, even though it actually created the Receipt.pdf file it was supposed to create successfully. (It still sent the email with the correct Receipt.pdf file attached successfully, despite the error message.)

As usual, please let me know of any testing results, whether positive or negative, either by email or by adding a Comment to this blog post. Thank you.

By the way, for those of you who responded to my last blog post about selecting a new Software4Nonprofits logo, and haven’t seen the new one  yet, it’s on the site now. It was a hard choice, because there was no strong winner among people’s votes, but I picked the one that did have the most votes, and which I personally liked quite a lot as well. Thanks to those of you who gave me your thoughts on that.

New logo options

October 18th, 2010

Hi DONATION advisors. I’m having my logo redesigned by a graphic designer, and have a bunch of options to choose from. If you could take a quick look at those options on the page http://stiao.com/s4np/fullpage.html and let me know which are your favourites, I’d very much appreciate it. You can see the current logo (which I’ve been told is “old fashioned”, at least in Internet years) at www.software4nonprofits.com, of course.

If you’re referring to the new options by number (the are labelled “Logo Set 1” through “Logo Set 17”), please be aware that those labels are above each image. Each image has a colour version and a black & white version, but I’m only really concerned about the colour version.

Thanks!

New Multi-Year Pledging Features

September 29th, 2010

I’m working with a fundraising consultant who helps churches with multi-year capital campaigns, and we are designing a set of improvements to DONATION to more properly handle multi-year pledges. (Currently, as you probably know, DONATION has only an Annual Pledge field for the current year’s pledge, which is assumed to be for the donor’s total donations.)

I’d like your comments on the following suggested set of features. Anything sound wrong? Anything missing? I’m not trying to cover every possible pledging situation at this point, just targeted multi-year campaigns, but if you feel that focus is inappropriate, do let me know.

  • Sort of like with the Donation Description field, add an option (in Maintenance -> Main Windows Options’ Donor Details tab) to add a drop-down arrow on the Annual Pledge field, that if clicked, brings up a small window for specifying multi-year pledge information. If this option is not selected (which by default it will not be) then multi-year pledging will not be supported in the program, and most of the following features will not appear. (Annual pledging will still work as it does now.)
  • If you do select that option, then if you click on the drop-down arrow in the Annual Pledge field, a small window will come up that allows you to enter the following fields:
    • Number of Years in the pledge. The control for this might be one of those controls that shows a number, and has up and down arrows to increase or decrease it, between specified limits (such as 1 to 10).
    • Start Date of pledge
    • End Date of pledge (not entered – calculated based on the previous two fields)
    • Total Pledge Amount (i.e. for the entire multi-year pledge period)
    • Perhaps also a not entered but calculated field for the annual pledge amount, which is the total divided by the number of years?
    • Drop-down for the Donation Category that the pledge is for. (This will show all categories, and also have an option “All Categories”, which means the pledge can be fulfilled by any donation the donor makes in any category. If a specific category, like “Capital Campaign”, is selected here, the pledge can only be fulfilled by donations in that category.)
    • A button to display the current Amount Outstanding (not yet paid) on the multi-year pledge. (I don’t think this should be displayed immediately and automatically, because it wouldn’t make sense while the user was filling in these fields, or while they were in the middle of changing them.)
  • If the user has entered multi-year pledge info in this way, then when they return to the main window, the field label “Annual Pledge” in the Donor Details area will change to something appropriate, like “5 Year Pledge”.
  • Also in Maintenance -> Main Windows Options’ Donor Details tab, there will be a drop-down for “Default Multi-Year Pledge Category”, with the same options as in the popup pledge details window – “All Categories”, plus all donation categories. If this has been specified, then whenever the multi-year pledge window is opened for a donor, where that info has not been previously filled in for that donor, this selection will be made automatically.
  • When you start a new year, with Maintenance -> Change Year -> Next Year, and it is copying the donor details from the one year to the next, all multi-year pledge fields will also be copied. The one exception will be pledges that have expired (their end date was in a previous year) – those will be deleted, but only from the new year’s donor record.
  • Two reports will be added (can you think of others that might be needed?):
    • One report with the columns donor name, start date and # of years (also end date?), category, pledge amount, and total given against that pledge (e.g. in the category) within the time range. Maybe also amount still outstanding? Sorted by name?
    • One report of only those who have fulfilled their whole pledge, sorted in descending date order of when it was fulfilled. For organizations that are collecting pledges through monthly pre-authorized debits, this could be used to determine when to turn off the preauthorized debits for those donors who have paid up in full.
  • Add mail-merge fields (at least to the Total Donations Information letters) for Total Pledge Amount, Pledge Duration (e.g. “5 year”), Pledge End Date, Total Pledge Paid, and Total Pledge Outstanding (unpaid so far). The three amount fields are already there, but will be re-interpreted to apply to multiple years in the case of multi-year pledging.
  • Add a sample mail-merge letter for informing donors about the status of their multi-year pledges.

That’s all I we have come up with so far in terms of requirements. Note that some things I am not proposing to handle are partial-year pledges (e.g. monthly or quarterly), or pledges for multiple categories (so much for the General fund, so much for the Building fund).

Please give me your comments, as usual ideally through a Reply to this blog posting. Thank you!

DONATION 3.31 Beta6: PDF Printer Fixes

August 1st, 2010

Hello again DONATION beta testers. Well, the new PDF printer in version 3.31 Beta3 that I informed you of recently worked for many people, but not for everyone. Some users, particularly those with Windows 7 and/or 64-bit computers (I think!) still had problems.

It turns out that the issue is that for some of those users, the Save PDF button on reports and built-in receipts (but not mail-merge letters and receipts) fails if the program is not run as a Windows Administrator. And I changed the program to stop running as an Administrator in version 3.30, to better follow Microsoft guidelines, and to stop those annoying User Account Control “Is it OK for this program to modify your computer?” prompts for users with Windows Vista or Windows 7.

The solution I ended up with (which I am not completely happy with, but can’t see how to improve on at this point) is that if you run DONATION normally (not as an Administrator), try Save PDF, and it fails, you get a message to re-run DONATION as an Administrator, re-do the action you just did, and do Save PDF from there.

Another option that does work, oddly, is instead of using Save PDF on those reports or built-in receipts, use the normal Print button, and in the printer dialog box that comes up, switch to the PDF printer, “novaPDF Pro v7 for DONATION”. N.B. for receipts, there is no printer dialog box, so you have to pre-select that printer using the Print Setup button before clicking Print. When you do this, you get novaPDF’s dialog box prompting for the filename to save the PDF file to, without the default paths and filenames that Save PDF prompts you with (in my dialog box), but it does work, even without running as Administrator.

If this all seems a bit mysterious to you (why some things work and some don’t). it is mysterious to me as well! That’s because it’s about how the novaPDF software (that I bought) works, which is out of my control. I have worked with their tech support folks on this, but haven’t received any better solution.

Anyways, if you could try this out (at http://www.software4nonprofits.com/pretest.htm as usual) prior to my releasing it to the main web site, that would be great. As usual, please let me know any testing results (positive or negative!) via  a Reply to this blog posting.

I don’t plan to email all users about the release of version 3.31 after I release it, because it just isn’t major enough to warrant that. Rather, I will inform any users about it who write to me about having problems with PDF printing. And of course, all new users will get this version.

Thank you.