I have had fun working with MS Access databases this week at work. I have created an MRB database that is set up to print out the completed form (for placing with the Work Order being processed) and emailing the appropriate Engineer that there are new items to be dispositioned and an attached copy of the information - all at the touch of a button. Additionally, I have created the procedures on how to use the new MRB system. All I'm waiting for is the okey-dokey from 3 people to implement the new system.
While working on creating the MRB database, I got a call from Sales asking me to work on their database. It was just minor work, changing a C of C form that is sent to one customer. That database was created back in 1996 or so, and the person that built it is no longer available, so I got the honors.
Let's just say that the person that built the Sales database didn't do anyone any favors. Sure, it works okay, but she could have named forms, reports, queries and macros so that one has a clue as to what they are without opening them up. Other things were not done as I would have done them either, which made the job slightly more difficult, but I finally managed to do the deed.
So, I went back working on the MRB database and created a table for the Customer name. I figured this would be the easy one as I could import the information from the Sales database. Wrong answer! The idiot less-than-helpfull person that created the Sales database did not make a table for that. In fact, she didn't make any tables except for the main table. Now I'm not an expert by any means but this person was supposedly an expert who was paid large amounts of money to create the database. She should have known better than that!
Well, anyway, I got the Customer names into a table for the MRB database and things should be all set. I got to put my brain to some hard work and learned some stuff along the way (like how to reset the auto-numbering, how to set up email capabilities amongst other things).
Sales was extremely gratefull that I could handle their little problem and the Engineer that gave me the job on building the MRB database was impressed that I got it done so quickly.
All in all, a good time at work.
Aha, Bogie, you have let the cat out of the bag. Now I know whom to tap for IT when I buy MS Access (which did not come with the XP version of MS Office--I'll have to change my OS.) No good job goes un-rewarded. More work will accrue. Great going!! (I know the challenge of designing an Access DB because I had to work with several people in setting up databases that I wanted my people to use. Making a database isn't hard. Making a GOOD database is an art. Our databases were eventually made SQL databases--but I couldn't see the differences from a user's perspective.)
I just got a flashback to a database that I used at Edwards AFB 20 years ago--that one of our young programmers did for us. It was written using Knowledgeman. (Is Knowledgeman still out there?) Another guy and I wrote a paper (that he presented at some professional meeting--I've forgotten which one--I didn't go) concerning planning for the future. The company awarded us some money, their being really big on their people's publishing. It enhanced our reputation as "experts", garnering more business.
Posted by: Cop Car | January 22, 2005 at 09:35 AM
Never heard of Knowledgeman - but that doesn't mean it's not still out there!
Posted by: bogie | January 23, 2005 at 02:56 PM