I am completely new to posting anything so please forgive me if I goof up. I'm educable.
First, I am creating an inventory management database (we have some special needs so a canned one won't work). We want to use barcodes. My database will have a master Product Table which will store a list of all the products we have and an Inventory Table which is where I will 'receive' the actual inventory we get. Other than that it will mostly be lookup tables. The Add Inventory Form will look to the Product Table to see if that item already exists in the Product Table with a link to add a new item to the Product Table.
I would normally think to put the barcode field in the Product Table except for this: while some products will all have the same barcode (latex gloves, large, McKesson) other things that have separate serial or VIN numbers will need separate barcodes like laptops or vehicles. This makes me think I need to put the barcode field in the Inventory table. So, first would that be correct?
Second, it would be nice if when I am putting a new product into the Product Table I can choose whether to add a barcode at that time or not. By that I mean if I'm adding latex gloves, large, McKesson I'd like to add the barcode there. But if it's something with a serial number, etc. I'd like to wait and enter the barcode when I add it to inventory as I would not capture the serial number for that item until that point. Any ideas how I do that??
This second question/idea would shorten data entry down the road as I'd only have to assign a barcode once for the more generic stuff (gloves) in the products table and have it show up in the Inventory table as I'm adding new inventory. BUT I would need the barcode field to be blank if there was no barcode added when it was added as a Product (e.g., because it had a specific serial number) AND I would need to be able to fill in that blank barcode field in my Inventory table and have it 'stick' to that inventory item.
If I can't do this I'm going to have to maintain a separate list of 'generic' items and their barcodes so I can find that barcode whenever I enter more of that item (e.g., gloves) into inventory which seems inefficient and open to items having another item's barcode by accident. And there is a lot of the 'generic' items.
I work for an emergency response program at a county health department and during an emergency or an exercise other people will be using the database. Unfortunately, because of the nature of my program, these people will have training every year or so and may use it during an exercise once every 2-3 years. Yes, we will provide them with some printed cheat sheets and during an exercise they'll be working on a copy of the database but if we have an actual emergency they will be working on the real thing. Some of these people may be good with databases but others will not. Meanwhile, I will be working in the database every day as I'm the one who maintains our inventory records. I can just see that separate barcode list becoming a problem.
Any ideas would be greatly appreciated.