I'm sorry to say, I saw that Shawn was online shortly after Allen emailed him. It would appear that he read this thread but didn't bother to respond.

Shawn,

WTF? You used to be my absolute hero! By just completely walking away without giving us a method to keep things working and up to date, you undo all the great legacy of your work. Imagine if you had invested many years of your time in developing a system, and the guy who wrote a core component to all of your work all of a sudden leaves and shows no indication of ever being contactable again. Well, you would be concerned wouldn't you? You'd be wondering how long it will be until the technology moves on to the point where key features are no longer supported, or even worse, it no longer works at all.

Then you'd be left with many years of your work down the drain :-(

Classic has a serious issue that results in the GUI not drawing correctly after extended use of forms that have a lot of detail in them. There are also scenarios with menus that trigger fatal exceptions. .NET is moving forward and it will only be a matter of time until the 2.0 framework is no longer supported.

I'm sure no one would expect you to do the same thing for the rest of your life. People need to move on and explore other things; just please don't leave us in the lurch.