Code Stuff and Boring Stuff

While I was at work yesterday I thought of a likely scenario in which my code wouldn't work. It saves an .xml file and I couldn't get it to work saving directly to C: so I had it save to a specific directory. Well, I had created this directory, most people wouldn't have a directory called "Test" on their computer, I assume, so I wanted to see what would happen if I deleted it. So I did and sure enough my program fell apart. Oh, I should mention that the dude had responded to my email saying he'd fix it so I could submit it online on Monday (so this bought me extra time to fix the problem!). Anyway, this morning I figured out a way to save it that would be flexible and it works! Now I'm seeing if I can throw in another extra: "Save" always works fine, but what if you have someone doing something they shouldn't like "Load" before a file is ever saved? I know the project doesn't NEED it, but I thought it'd be a nice touch if I added an error message for that scenario. Haven't gotten it figured out yet, but we'll see what the next few minutes can do. Last night towards the end of my shift I got stuck doing the most boring job ever (counting checks). Ugh. Why couldn't they just let me stay on the fucking scanner all night like usual?