![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
The weekend was both fairly enjoyable and productive, an unusual combination.
Friday was a day off from Marlin. They very unexpectedly gave us the day off, making for a long weekend. I went into United Health Care with Monique and worked with her new db designer answering a lot of his questions for the aspects of this project that he is taking over. Then I spent the rest of the day working on my part of the db. I've got to say, I LOVE my new laptop. This thing just flies, no matter how much stuff I have open. It really boosted my productivity.
Saturday, Monique and I went into her work again. While I was working on the database I was also loading some of my CD collection onto my computer to get on my new iPod. It demonstrated again how much I love my new laptop. I had only loaded a couple CDs on my old computer and every time I was doing it, the CPU was completely maxed out and I couldn't do anything else. The new laptop not only didn't break a sweat, but also let me have several instances of Access and SQL server open while it was doing it. Just out of curiosity I watched the task manager for a bit while I was working and never saw it go over 70%. Wheeeee! I know, I'm sounding like a geek. Just let me enjoy it.
I hit a huge snag Saturday that really screwed me over, cost me several hours. I'm going geek again. Fair warning. I have a query that needs to select only the first record that meets the criteria. This is very easy. There's a SQL statement that starts out with "SELECT TOP x" where x = the number of records you want. In my case, I put a one there and SQL picks the first record. Access however picked 2 records, which totally messed me up. Of course, it only started displaying this stupid behavior when I started doing larger data sampling, so it I had to go way back to the beginning of things I'd worked on Friday to change things. I spent hours trying to fix this unexpected problem and it set me way back. There were times I wanted to cry. It was so frustrating. So much wasted time.
Sunday, we took down all the Christmas decorations and (mostly) cleaned the house before going back to more database work. I figured out my problem from the previous day and made a bit more progress, but still failed to meet my deliverable goal for turning it over to Frank (the db developer at UHC).
Flute choir rehearsal was ok. We have a new member. She is an excellent player. We had several of our regular members out, so we were still a little thin on numbers. And early on in the rehearsal, my head cork popped out of my bass flute. Fortunately, Cathi, the new member had a bass flute and let me use it for the rest of the rehearsal. I can see why she's not fond of it and doesn't want to play it herself. The low octave is horribly unresponsive. I guess I'm just going to have to get mine fixed quickly. I think it's going to be time for a new one some time this year. *sigh*
Friday was a day off from Marlin. They very unexpectedly gave us the day off, making for a long weekend. I went into United Health Care with Monique and worked with her new db designer answering a lot of his questions for the aspects of this project that he is taking over. Then I spent the rest of the day working on my part of the db. I've got to say, I LOVE my new laptop. This thing just flies, no matter how much stuff I have open. It really boosted my productivity.
Saturday, Monique and I went into her work again. While I was working on the database I was also loading some of my CD collection onto my computer to get on my new iPod. It demonstrated again how much I love my new laptop. I had only loaded a couple CDs on my old computer and every time I was doing it, the CPU was completely maxed out and I couldn't do anything else. The new laptop not only didn't break a sweat, but also let me have several instances of Access and SQL server open while it was doing it. Just out of curiosity I watched the task manager for a bit while I was working and never saw it go over 70%. Wheeeee! I know, I'm sounding like a geek. Just let me enjoy it.
I hit a huge snag Saturday that really screwed me over, cost me several hours. I'm going geek again. Fair warning. I have a query that needs to select only the first record that meets the criteria. This is very easy. There's a SQL statement that starts out with "SELECT TOP x" where x = the number of records you want. In my case, I put a one there and SQL picks the first record. Access however picked 2 records, which totally messed me up. Of course, it only started displaying this stupid behavior when I started doing larger data sampling, so it I had to go way back to the beginning of things I'd worked on Friday to change things. I spent hours trying to fix this unexpected problem and it set me way back. There were times I wanted to cry. It was so frustrating. So much wasted time.
Sunday, we took down all the Christmas decorations and (mostly) cleaned the house before going back to more database work. I figured out my problem from the previous day and made a bit more progress, but still failed to meet my deliverable goal for turning it over to Frank (the db developer at UHC).
Flute choir rehearsal was ok. We have a new member. She is an excellent player. We had several of our regular members out, so we were still a little thin on numbers. And early on in the rehearsal, my head cork popped out of my bass flute. Fortunately, Cathi, the new member had a bass flute and let me use it for the rest of the rehearsal. I can see why she's not fond of it and doesn't want to play it herself. The low octave is horribly unresponsive. I guess I'm just going to have to get mine fixed quickly. I think it's going to be time for a new one some time this year. *sigh*
