No, I do NOT belong to the writers guild, and am NOT on strike. So much to say, so little time in which to say it!
I awoke this morning thinking about my latest quandary — whether to just give up on maintaining the non-working component of my application, or to continue my efforts to come out of my predicament by means of a “breakthrough” which suddenly fixes the problem. (So far this morning I have chosen to blog about it instead of working on it — somehow hoping that I talk my way through to a fix.)
The problem? An application which simply refuses to print properly from the clients brand new Vista workstation — which by the way I encouraged them to get believing that Vista is in our future whether we like it or not! My bad! It is one of those situations where I look at the issue, and no matter what I consider, and no matter what I have done with the debugger to this point, the answer I come up with is always (…it SHOULD work!).
Dealing with this issue for the last few days has brought me back again to the issue of “When is it time to redesign?” I have been avoiding attempting a complete redesign in this case for a few reasons — it works well on all but this new Vista workstation — it has worked for the last 4 years — it is not code that is out-of-date as is some that I have referenced here in my blog! In any redesign of this application component it is highly desireable to maintain the same look, feel and flow of the program (…often not exactly a no-brainer to do). For all of these reasons, I have avoided what appears to me at this point as my only choice – redesign. Since this component of this application is the only one where I have run into any problems, I am encouraged to spend the time and attempt to re-design this process so that it will work properly.
Bottom Line might be — If it ain’t broke — (sometimes fix it) — if it is broke — ReDesign!