RE: Index or primary key cannot contain a null value.
- From: Klatuu <Klatuu@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 6 Sep 2005 17:05:22 -0700
I really don't think so. You may be able to accomplish this, but still, the
reason you are having problems is design. In your original post, you said it
may be a child on more than one form. Already, you are in trouble. How can
you identify the parent if you have only the child?
"JohnLute" wrote:
> I guess there are exceptions to every rule. Here's an example of my design:
>
> tblPKCorrugatedFinishingAttributes is a parent to tblPKProfilesQualifications.
>
> In this instance, a record for tblPKProfilesQualifications may exist without
> a record in tblPKCorrugatedFinishingAttributes. Why? Because a corrugated may
> not have a specific finishing attribute defined but may have several
> qualifications.
>
> In other words, qualifications are finishing attributes and are properly
> assigned as children of tblPKCorrugatedFinishingAttributes.
>
> Is there a before/after update event that can create a parent record?
>
> --
> www.Marzetti.com
>
>
> "Klatuu" wrote:
>
> > The real problem here is database design. There should never be an instance
> > where a child exists without a parent.
> >
> > "JohnLute" wrote:
> >
> > > I have a subform (sfrmPKProfilesQualifications) that's used in multiple
> > > subforms. The problem I have is that there are instances when
> > > sfrmPKProfilesQualifications will have a record and it's parent subform will
> > > not. Of course, this results in the error:
> > >
> > > "Index or primary key cannot contain a null value."
> > >
> > > I suppose an easy fix to this would be to move sfrmPKProfilesQualifications
> > > out of the subforms, however, I wanted to explore if there's a Before/After
> > > Update code that I could insert into it that would create the primary key
> > > record.
> > >
> > > Thanks in advance for your time!
> > >
> > > --
> > > www.Marzetti.com
.
- Follow-Ups:
- RE: Index or primary key cannot contain a null value.
- From: JohnLute
- RE: Index or primary key cannot contain a null value.
- References:
- Index or primary key cannot contain a null value.
- From: JohnLute
- RE: Index or primary key cannot contain a null value.
- From: Klatuu
- RE: Index or primary key cannot contain a null value.
- From: JohnLute
- Index or primary key cannot contain a null value.
- Prev by Date: Re: importing access 2003 reference into access 2000
- Next by Date: Re: Specifying a Printer
- Previous by thread: RE: Index or primary key cannot contain a null value.
- Next by thread: RE: Index or primary key cannot contain a null value.
- Index(es):
Relevant Pages
|