I understand the normalization process I would have one record for one Primer associated to one Caliber, right. There are in my DB thirteen different Primer Types,
Small Pistol, Small Pistol Magnum, Small Pistol Match
Large Pistol, Large Pistol Magnum, Large Pistol Match
Small Rifle, Small Rifle Magnum, Small Rifle Match, Small Rifle Military Magnum
Large Rifle, Large Rifle Match, Large Rifle Magnum Match
Now with thirteen (13) different Primer Types times eleven (11) different Calibers, creating One Hundred and Forty Three (143) Records using a Normalized Database.
My Database has only thirteen (13) records one for each Primer Type and three Fields to cover all calibers associated with one Primer. And no future Calibers. I know Not Normalized.
We could do the same math as above to calculate total records needed for the Two Hundred and Two (202) different Powder Types which cover
the Eleven Calibers and creating Two Thousand Two Hundred and Twenty Two (2,222) more Records.
Now all the Brass and Projectile's are UNIQUE as they will only fit one Caliber and every Caliber will appear in the Field Caliber1 and this is where
my problem comes to light. To find out how many Cartridges I can reload I need the SQL to not just look at Caliber1 but also scan Caliber2 and Caliber3 for a Caliber match, this will cover all possibilities of the selected Caliber appearing in Caliber2 or Caliber3 when looking for possible Powder and Primers.
A WHERE statement in the SQL will take care of this problem. I don't know SQL so I need someone's help. This is as close as I can get:
Code:
WHERE [tStock]![Caliber1] = cboCaliber OR [tStock]![Caliber2] = cboCaliber OR [tStock]![Caliber3] = cboCaliber