max.wanadoo at gmail.com
max.wanadoo at gmail.com
Fri Sep 28 08:43:02 CDT 2007
Arthur, That is just so easy to do. My code is riddled with them. All subtle and all designed to pop-up at the least opportune moment. In fact, I am not even going to enter the competition cos I will win hands down! On second thoughs - what prize are you offering? Max Ps. I used to subscribe to that publication and to the Foxpro one and the Access one. No wonder I developed such bad habits (grin). Pps. When you find the reason why your "Object Variable not set" is not working, you are forbidden to submit it as one of the entries. Ok? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Friday, September 28, 2007 2:28 PM To: Access Developers discussion and problem solving Subject: Re: [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 > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com