The Best Approach

[treb107]

I am the Asst. Quartermaster of our sizable Pipes and Drums Band. I have been tasked with devising and
maintaining an Inventory Control Program. I've built a serviceable Access Program that basically tracks items and locations. Using Queries gives me good reporting on the location of assets however the updating of individual items moving in and out of Stores is time consuming.
We have a Central Stores location and Members are issued standard sets of uniform, instruments, etc. which are referred to as Issue. I realize that moving items in and out of inventory using a form that lists the entire Issue would be much faster. Items being issued would diminish in Stores while an Issue being returned would increase Stores. My question is would I be better continuing to build an Access Program or would Excel be a better platform for my needs?

I am truly just a beginner so please answer in English.

 

[bdb04]

Without fully knowing your table structure, it is hard to get specific, but on the surface, it appears that Access should easily be able to handle your needs. Alot depends on whether or not each individual piece of equipment (pants, shirt, instrument, etc.) has its own independent ID number or if an entire set (probably not) is its own entity.

Either way, it should be fairly easy enough to "check out" whatever equipment is issued to a member. Again, hard to give specifics without more details, but on the surface, you could have a form with text boxes for each piece of a standard "issue" on it and a text box for member ID as well. You enter the ID numbers of each piece of equipment and the member number it is assigned to. You also have a command button on the form with some code behind it to update your tables to show those items are checked out to that member.

 

[treb107]

Thank You for that. The Program was built with Access 97 and I am now running 2007 and although conversion is running well I'm having difficulty using new version. Currently each piece of equipment carries an ID, should I have an Issue carry its own ID?

 

[bdb04]

Unfortunately, I can't help you much with 2007 specific info. I was a beta tester and hated it and removed it from my machine. It sounds like your current set up is the way it should be...each piece of equipment has its own ID. I would tend to stay away from having an issue having its own ID personally, but I can see a scenario where it would work. You would really want to be careful doing it that way though as it could lead to a normalization nightmare if you aren't careful.

Try what I had mentioned in my previous post and if you get stuck, post back with the problems you are having.