Today consisted of a few tweaks/enhancements to the SOCCED web app.
Primarily changing up a couple database admin screens to allow for a couple of new fields that were added. This included adding a couple of combo boxes and a bit of validation logic.
I also began setting up a couple of reports to provide a bit more functionality for the client within the interface.
Today consisted of some more bug fixing on the Socced site. Fixed a problem with an email that wasn’t giving the appropriate information. Also setup an email so that it would read more appropriately and give more information than the basics it was setup for.
Also had to fix a handful of procs to resolve some date checking issues. Fixed another issue that was storing information we shouldn’t have been storing.
Well, back after the long weekend. What an exhausting weekend too, but that is a post for another blog.
Today was a slow day, most of which was spent cleaning up minor details and tweaking some code to make it slightly more efficient and such.
All useful things to do but not terribly interesting to work on.
Bugs.
Actually that was yesterday’s tag line as well. Today was about half and half. Dealt with a number of bugs not the least of which was a next business day calculation that was being thrown off because I forgot to include a year check. Checking for next business day isn’t too bad until you include holidays in the mix. The way I checked for holidays was to simply check for the day # of the year. I.E. Memorial day 2007 is day # 145. Unfortunately I forgot to consider that eventually Memorial day would have the same day #. So I added a quick check to ensure that I only checked the dates that matched this year. After all there can only be one day # 145 in any given year.
Other bugs were concentrated in SOCCED and were equally easy to resolve upon discovering their source. I also had to upload a few additional records in the SOCCED system which took a bit longer because the data I was given was not entirely accurate and therefore required a bit of…creative interpretation.
The other half of the day (and the halves were intermixed…no particular time blocks devoted to either) was spent working on various grids filling in data. The hardest part of which is (as has been the case thus far) not assembling the data but finding the appropriate places to grab the data from and ensuring that I am in fact grabbing the appropriate data.
I’ve still got a few minor bugs to work out but for the most part all the data is appearing as it should be.
Bugs.
Today was spent almost entirely fixing bugs. A little time was spent figuring out what I will work on tomorrow but for the most part I started with a few minor bug fixes I knew about and knew how to fix in one system and then receiving several emails about some bug fixes related to data in a system I haven’t worked with/in for at least 2 weeks.
So I dug around and found the easy ones first and got them taken care of and then proceeded to email back and forth to clarify just what it was I was looking for in the system that was supposedly a bug. There are still a few that are “technically” outstanding but they don’t seem to be reproducable by anyone so they’ll “remain” for the time being until they pop up again and we can hopefully reproduce them enough to discover where the problem is occurring.
Like your mechanic says (at least to himself) if it ain’t broke, I can’t fix it.
WAAAAAAAHHHHH.
Sigh. What a day. Spent the day chasing down little bugs here and there and eradicating them. The morning was spent sorting out a Data Grid which was a much easier solution than what I was going for. Fine by me.
The next problem I faced was getting data to appear in the grid. But I took care of that fairly handily.
Final problem of the day involved realizing changes in the data grid in the update procedure for the back end. This involved more erasure of data. Fortunately I didn’t wipe an entire table this time. Finally figured out what was causing the wipes. Took care of that and got everything on track just in time to write this blog.
Tomorrow should bring something new to play with. Either that or bug fixes for all the code/procs I wrote today.
Things progressed smoothly until 4pm when I had to work on the final piece of the data puzzle.
Final result: I hate data.
Wow. Here we go…another week.
Started off with some…interesting developments. Literally. I popped up the applications I worked on last week and there were quite a few changes. The more I looked the more changes I found. Then I checked the version history on one of the files and discovered that one of the owners had been in there tweaking my code. No big deal…I figured it was a good/bad type situation.
Bad because he was in there changing my code. Good because he didn’t change a lot and what he did change improved it and made it more elegant. In any event I figured I was in for a quick debriefing of the changes and why he made them etc. and I was right. It boiled down to my unfamiliarity with the databases and some internal coding techniques.
At any rate today I slapped together 3 pop-up screens and got the layouts working correctly. Tomorrow will entail populating data fields galore. HOPEFULLY that will go quickly and smoothly. I shouldn’t have to copy too many procs for this one so I don’t anticipate any problems beyond finding the appropriate procs and figuring out how to access the data.
I continue to work on save functionality. I was able to get past the prior blockage thanks to Jerome. I obviously have a long ways to go in understanding the interactions between the database and the C# code.
The rest of the day was spent setting up save procs for the transaction detail screen. I made some decent progress, realized a bit late that I could’ve made more progress if I’d pulled up a different page that is doing exactly the same thing for the most part. Oh well…that’ll be monday I guess.
Ugh.
Working on writing save functionality for Transaction Details Screen. It’s being an unwieldy monster trying to sort it out. XML/Datareader problems are plaguing me at the moment.
The error just popped up out of no where and I’m not sure why. Debugging is near impossible because it seems to be a problem in the database rather than with the application.
