I sure bring some odd stuff to this forum, eh? It's probably because I'm
creating an odd or unusual database that Access was probably not intended to
service. Keep in mind that I'm housing packaging specifications which have a
broad range of data as they include glass and plastic bottles, corrugated
containers, plastic bags and cups, laminated film, etc.
I'll try to express my "logic."
Each packaging specification has a Profile. Each Profile relates to
Physical, Material, Performance, and Finishing Attribute tables. In the
example I previously gave there are Qualifications for each packaging spec.
Therefore, I created tblPKProfilesQualifications in a many-to-one
relationship with tblProfiles. Since Qualifications are a part of Finishing
Attributes, I created sfrmPKProfilesQualifications and made it a child to all
of the Finishing Attributes subforms.
Of course, this results in a parent record beng required in the Finishing
Attributes subforms before a record can be created in
sfrmPKProfilesQualifications. However, there are instances when there
Qualifications specified but no Finishing Attributes. Of course, this results
in "Index or primary key cannot contain a null value." To "override" this I
simply create a "dummy" value in any of the Finishing Attributes fields which
then creates a parent record in the Finishing Attributes table. I then delete
the "dummy" value and enter in the records in sfrmPKProfilesQualifications.
I would prefer not to have to create the "dummy" value as this is a bit
quirky and will confuse other users. I was thinking a before/after update
event might do the trick...?
Thanks for your time!!!