Skip to main content

How do I Install PenPal Pro?

So now you have decided to check out PenPal Pro, the penpal database, to help you keep track of all the letters and other things you send to all your friends and correspondents. How do you do that?

First, download the latest copy to your computer by clicking here. You may be asked to sign in or to sign up for an account - close the pop-up, an account is not needed to download the file. The file is almost 60 MB, and may take a few minutes to download to your computer. Save it somewhere you can find it, like your desktop.

Next, extract the files from the zipped downloaded file. You might do this by right-clicking on the file and selecting "extract" or by double-clicking on it and selecting "extract." This will unpack all the files into a new folder named "PenPal-Pro v2_2" (unless you choose another place).

Next, open the PenPal-Pro v2_2 folder and double-click on Setup to install PenPal Pro. If a security warning pops up, click Run

You should now see the PenPal Pro 2.2 Setup wizard. Click Next to begin.

The End-User License Agreement gives you a chance to review the terms and conditions for using PenPal Pro. Choose "I accept" and click Next to continue.

Enter a User Name and Organization if you wish (optional) and click Next

Choose Typical (recommended) or Custom setup, then click Install to begin. The wizard will then install all the pieces you need to run PenPal Pro in a folder named PPPro under your My Documents folder, and will put the Microsoft Office Access Runtime in an appropriate system area of your computer.

Ta-da! That's all there is to it. You should now be able to run PenPal Pro by double-clicking on the new icon on your desktop, or by clicking on the Start button and finding it in your menu of programs.

Popular posts from this blog

How to do Git Rebase in Eclipse

This is an abbreviated version of a fuller post about Git Rebase in Eclipse. See the longer one here : One side-effect of merging Git branches is that it leaves a Merge commit. This can create a history view something like: The clutter of parallel lines shows the life spans of those local branches, and extra commits (nine in the above screen-shot, marked by the green arrows icon). Check out this extreme-case history:  http://agentdero.cachefly.net/unethicalblogger.com/images/branch_madness.jpeg Merge Commits show all the gory details of how the code base evolved. For some teams, that’s what they want or need, all the time. Others may find it unnecessarily long and cluttered. They prefer the history to tell the bigger story, and not dwell on tiny details like every trivial Merge-commit. Git Rebase offers us 2 benefits over Git Merge: First, Rebase allows us to clean up a set of local commits before pushing them to the shared, central repository. For this

Java 8: Rewrite For-loops using Stream API

Java 8 Tip: Anytime you write a Java For-loop, ask yourself if you can rewrite it with the Streams API. Now that I have moved to Java 8 in my work and home development, whenever I want to use a For-loop, I write it and then see if I can rewrite it using the Stream API. For example: I have an object called myThing, some Collection-like data structure which contains an arbitrary number of Fields. Something has happened, and I want to set all of the fields to some common state, in my case "Hidden"

Git Reset in Eclipse

Using Git and the Eclipse IDE, you have a series of commits in your branch history, but need to back up to an earlier version. The Git Reset feature is a powerful tool with just a whiff of danger, and is accessible with just a couple clicks in Eclipse. In Eclipse, switch to the History view. In my example it shows a series of 3 changes, 3 separate committed versions of the Person file. After commit 6d5ef3e, the HEAD (shown), Index, and Working Directory all have the same version, Person 3.0.

Code Coverage in C#.NET Unit Tests - Setting up OpenCover

The purpose of this post is to be a brain-dump for how we set up and used OpenCover and ReportGenerator command-line tools for code coverage analysis and reporting in our projects. The documentation made some assumptions that took some digging to fully understand, so to save my (and maybe others') time and effort in the future, here are my notes. Our project, which I will call CEP for short, includes a handful of sub-projects within the same solution. They are a mix of Web APIs, ASP MVC applications and Class libraries. For Unit Tests, we chose to write them using the MSTest framework, along with the Moq mocking framework. As the various sub-projects evolved, we needed to know more about the coverage of our automated tests. What classes, methods and instructions had tests exercising them, and what ones did not? Code Coverage tools are conveniently built-in for Visual Studio 2017 Enterprise Edition, but not for our Professional Edition installations. Much less for any Commun

Scala Collections: A Group of groupBy() Examples

Scala provides a rich Collections API. Let's look at the useful groupBy() function. What does groupBy() do? It takes a collection, assesses each item in that collection against a discriminator function, and returns a Map data structure. Each key in the returned map is a distinct result of the discriminator function, and the key's corresponding value is another collection which contains all elements of the original one that evaluate the same way against the discriminator function. So, for example, here is a collection of Strings: val sports = Seq ("baseball", "ice hockey", "football", "basketball", "110m hurdles", "field hockey") Running it through the Scala interpreter produces this output showing our value's definition: sports: Seq[String] = List(baseball, ice hockey, football, basketball, 110m hurdles, field hockey) We can group those sports names by, say, their first letter. To do so, we need a disc