[AccessD] Friday (You Know)

Back in the days of DOS, Pinnacle Publications had a Clipper Advisor
magazine, for which I wrote a column called Seek And Destroy. The idea was
that I would present some code containing a bug and challenge the reader to
detect the bug. The first few columns were easy, but as the months passed I
found it increasingly difficult to come up with a non-obvious bug. This may
not be further proof of my conjecture, but it is an interesting exercise.
Try to write a buggy routine. Nothing obvious like an a misspelled variable
name or an array-boundary error. It's got to be subtle.

A.

On 9/28/07, max.wanadoo at gmail.com <max.wanadoo at gmail.com> wrote:
>
> The reason they are not bugs is because in my software they are known as
> "Hidden Easter Egg Features" and the person who finds them gets a prize.
> First prize being the ability to be the first to test the update.
>
> Problems are merely "challenges"
>
> Max
>