OK. I've got another job. Sadly like all my other jobs this one involves a lot of work for no pay , but I digress. I'm building a database to track information on group members and I'm thrashing out the organization of it. It is pretty easy to wind up having an entry take up more than one page, and some of the fields are only going to be used rarely (but are needed). I'd also like to be able to "drill down" into entries. For instance I want to be able to just list the major, top-level goal each person is working on, but I'd like to be able to link fields to a more detailed entry on where they are on sub-tasks--tracking progress. ...I really need to create a database if I want anything that complex, don't I?
Yep, that sounds like a job forrrr.... du duh duh doooooo Microsoft Access, the worlds most annoying programme
Dude, what's up with all these jobs for no fucking pay? Do I have to point you to my dog eared copy of Atlas Shrugged?
wait til the mexicans find out they can get hired for below minimum-wage, and then foist the job on to volpone at a tidy profit...
Wrestling with Office (and a 7 year old version, at that) makes me want to murder Bill Gates with a hammer. If the database wasn't so phenomenally annoying to work with I'd be using the right tool for the job. Because it is arguably the most user-unfriendly piece of mainstream software on the market, I'm trying to make a spreadsheet do the job of a database. Which is a bit like trying to build a cabinet with a handsaw, an electric drill, and a tape measure. So for some reason, the bastard won't let me sort the thing by fields. Well, it will let me sort by fields. But for some reason it only sorts PART of the thing by fields. That doesn't do me a whole lot of good, as I sort of want the e-mail addresses of people to correspond to the person I want to contact.
meh, access is far from the worst thing i've enountered, and since 2000 has actually been okay - not that i'd normally admit that of course. couldn't you do the thing in sql server express with an intranet, if they can't afford to shell out for a decent RAD tool?
This really sounds like something that should be done on a database. Look at it as an opportunity to brush up a new skill set. If you aren't being paid, you should at least try to get a few new resume points out of it.
At some point in this project, someone's going to say: 'oh yeah, did we mention we want to be able to access and edit this on the net?' Use a database. For this stuff, access is easy enough to use (if their website supports asp).
