Saturday, February 16, 2008

Bad Programming as Punishment

My wife and I both spent a very long and, for me, disappointingly unproductive, day at the office today. I worked on creating a new database system for one of our clients and got only about half as much done as I expected I would. That's partly because I'm not a very good Access programmer and because I am more confident in my abilities than I should be.

After importing a massive set of files into Access, I went about the task of identifying--or tring to identify--each field. I had not documentation, so it was a bitch. Whoever built the database from which I was trying to convert the data decided, for reasons beyond my compehension, to separate area codes and telephone numbers from one another. And, of course, they were physically separated in the file structure, as well. I managed to figure out which was which and then managed to append the contents of the area code fields onto the front-sides of the phone numbers. What I managed to do then, though, was to erase almost the entire contents of all the telephone number fields, thanks to some "fancy" footwork designed to enhance the records. I didn't test my routines, of course. So, I'm being punished by bad programming for being such an idiot.

At any rate, I have to spend tomorrow doing the undone elements from today. I need an IT person; I am not one, but have fallen in to the role out of necessity. I'm a much better cook. This evening, we had chicken flautas, courtesy of my urge to make them a couple of nights ago. It was a good thing I'd made them before, considering how late we worked today.

I really, truly don't want to work tomorrow. But, I really, truly must.

No comments:

Post a Comment