Really Bad Code
So I'm rewritting an application leftover from the previous consultant. I know I've talked about this before, but this one is really bad.
( Bad Programmer, No Coffee! )
( Bad Programmer, No Coffee! )
Oops!
Well I was making pretty good progress today until I used the wrong function and instead of inserting a block of data into a workbook page I deleted and replaced the entire thing. Oops, indeed. Luckily I have a not terribly old backup and most of the work of the last week has been planning or working in a different file. Yes, I have to recreate a lot of the tedious bits that I did yesterday, but at least I know what and where to rebuild and I won't have to spend as much time on it.
I also have a nice new backup in no less than two places.
I also have a nice new backup in no less than two places.
Stupid Microsoft Tricks
I am working on a project to convert the prior programmer's horrible Excel "database" spaghetti code application into something that can actually be updated and maintained. Of course the end users, being accountants, want both the results and the interface to remain in an Excel workbook. Yeah, yeah, I can do that ...
Warning: Geeky programming stuff ahead!
( Enter the Stupidity For A New Age ... )
... and then I shot 'em.
Warning: Geeky programming stuff ahead!
( Enter the Stupidity For A New Age ... )
... and then I shot 'em.
