...and I'm ready to go home. This post could also be titled, "Didja ever have one of those days?"

I thought I'd share some of my day with everyone, just so you know if you've had a bad day, you're not alone.

I've been working on this project that has to print out a diagram based on some of its calculations. To do this it has to interface with either Excel or Lotus 1-2-3, depending on which the user has on his computer. I've mentioned this problem in the past, and had a abstract class setup to define the basic interface.

Earlier to-day I started testing the new class. I running into the problem that the variable holding the reference to the server was NULL. Couldn't figure out what was going on. After about an hour, it finally hit me. The diagram printer was based on the abstract class, which, since it merely defined the interface, didn't create the object.

OK, so I throw in This.oServer = CREATEOBJECT('Excel.Application') and figure I'm good to go. Now it won't load the templet file. Another hour passes, then it hits me, It's the abstract class, dummy! None of those methods actually do anything!

So I make the necessary adjustments. Everything should be fine now, right! Wrong! It hits the line This.PrintDriagram, and it can't find the method. Another hour passes, which includes me using AMEMBERS(), the debugger and re-examining the class several before I realize the method is PrintDiagram, not PrintDriagram. Sheesh!

I've now got a nicely dented forehead from going "Doh!" (whack! as the butt of my palm strikes my forehead).

Can I leave now? Time to "Crack a cold one - East of Java Beans":-)