Life Has Just Gotten Easier

This is going to be a "short and sweet" blog. OK, since I was vaccinated with a phonograph needle, it will be as "short" as *I* can make it.

The purpose of this blog is twofold. First, to help spread the word about a Visual FoxPro issue (and the solution) that has been annoying me for several years. Second, to give credit where credit is due and point you to the source of the solution; namely a recent Doug Hennig blog.

As I said, it has been an annoying issue, but one that was not so bad as to actually cause me to get off my big, fat fanny and do something about it. Fortunately, the ever-tenacious Doug Hennig did and was generous enough (isn't he always?) to publish his findings.

OK, the issue is... most of us Visual FoxPro developers know that it is good form to NOT save the printer environment with the report form. Sorry, but if you do not know this, it is a topic for discussion at another time. Or you could "Google it". Nevertheless, as diligent as I may be in not saving the printer environment, there have been times where it was saved. I could never capture that point in the development of the report form when it happened. The main reason for that is because (usually) when I noticed the printer environment had been saved, it was way past the point at which it happened. Like I said, annoying like a gnat buzzing around your face at a picnic; not like a nine inch nail driven into your brain.

Enter Doug Hennig to the rescue. I am not going to reveal the solution here, but suffice to say that it is a relatively easy fix which can be accomplished in about five minutes. Here is the URL to Doug's blog... http://doughennig.blogspot.com/ Look for the blog entitled, "Fixing a Report Designer Bug".

Thanks again, Doug for sharing.