Believe me if I could have bought an app to do this I would have. Last time I did anything with Access was 7.0, more years ago than I care to remember and that was for a class project.
What I'm trying to do is keep track of cuts of meat stored in different freezers and then in different containers in each freezer. So I've created a table with a PK, cut_code, cut_name, pkg_weight, price_lb, pkg_price, breed_name, freezer, location, date_processed.
If I am remembering correctly, and reading Access 2007 for Dummies isn't helping as much as I'd hoped, I want to create separate tables for anything I'm going to be entering multiple times? That would be the cut_name, price_lb, breed_name, freezer, location, date_processed fields. Am I making this harder on myself than it needs to be by creating all those tables? As far as size of the database is concerned at any given time we've got anywhere from no product to as much as 3,000 pkgs of meat.
I think I can handle the forms and queries once I get the design nailed down. What would really be fun would be finding an algorithm that would allow me to query how many of a certain cut I have on hand and then how many "family packs" I could produce using the weights of the packages and optimizing for say a 10lb family pack.
Currently I'm lambing, got sows giving birth, up to my shins in mud and it's still snowing so any help would be greatly appreciated. Not having an accurate inventory is cutting down on our efficiency, costing us time and money. Like to get this project nailed down before the Farmers' Market season starts up.