[AccessD] matching field error

Andy Lacey andy at minstersystems.co.uk
Fri Dec 12 05:31:09 CST 2003


No not really I'm afraid. Anyone else?

--
Andy Lacey
http://www.minstersystems.co.uk




--------- Original Message --------
From: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
To: "AccessD at databaseadvisors.com" <AccessD at databaseadvisors.com>
Subject: RE: [AccessD] matching field error
Date: 12/12/03 11:23


Sorry i mistyped: The default is Null (empty).
With 0, zero, null it seems to be that i sometimes type something different
as a think. Sorry for this.

Any new ideas?

Pedro




In antwoord op:

> From: "Andy Lacey" <andy at minstersystems.co.uk>
> To: "'Access Developers discussion and problem solving'"
> Date: Fri, 12 Dec 2003 07:34:29 -0000
> Subject: RE: [AccessD] matching field error
>
>
> Actually Pedro you said the default is zero (see your previous post below)
,
> so we thought that was it.
>
> Andy Lacey
> http://www.minstersystems.co.uk
>
>
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > Pedro Janssen
> > Sent: 11 December 2003 21:56
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] matching field error
> >
> >
> > Hello Andy and Charlotte,
> >
> > i explained before that the default value pro[perty of
> > PrTestID is empty (no
> > value) so this can't be the problem.
> >
> > Pedro
> >
> >
> > ----- Original Message -----
> > From: "Andy Lacey" <andy at minstersystems.co.uk>
> > To: "'Access Developers discussion and problem solving'"
> > <accessd at databaseadvisors.com>
> > Sent: Wednesday, December 10, 2003 10:51 PM
> > Subject: RE: [AccessD] matching field error
> >
> >
> > > Well thought Charlotte, that sounds like the issue. Pedro,
> > change the
> > > properties of PrTestiD by removing its default value and
> > see if that
> > > cures it.
> > >
> > > Andy Lacey
> > > http://www.minstersystems.co.uk
> > >
> > > > -----Original Message-----
> > > > From: accessd-bounces at databaseadvisors.com
> > > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> > Of Charlotte
> > > > Foust
> > > > Sent: 10 December 2003 20:52
> > > > To: Access Developers discussion and problem solving
> > > > Subject: RE: [AccessD] matching field error
> > > >
> > > >
> > > > The point is that if you don't have a record in the lookup table
> > > > with zero as its primary key, having a default of zero will cause
> > > > you problems with referential integrity in place.
> > > >
> > > > Charlotte Foust
> > > >
> > > > -----Original Message-----
> > > > From: Pedro Janssen [mailto:pedro at plex.nl]
> > > > Sent: Wednesday, December 10, 2003 11:30 AM
> > > > To: Access Developers discussion and problem solving
> > > > Subject: Re: [AccessD] matching field error
> > > >
> > > >
> > > > The default value is zero, so this isn't the problem. Thanks for
> > > > thinking with me.
> > > >
> > > > Anyone else some ideas.
> > > >
> > > > Pedro
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Charlotte Foust" <cfoust at infostatsystems.com>
> > > > To: "Access Developers discussion and problem solving"
> > > > <accessd at databaseadvisors.com>
> > > > Sent: Wednesday, December 10, 2003 5:51 PM
> > > > Subject: RE: [AccessD] matching field error
> > > >
> > > >
> > > > > Unless it is specifically set to null, a numeric field
> > usually has
> > > > > a default value of zero. If you're dealing with numeric keys,
> > > > > this might be tripping you up.
> > > > >
> > > > > Charlotte Foust
> > > > >
> > > > > -----Original Message-----
> > > > > From: pedro at plex.nl [mailto:pedro at plex.nl]
> > > > > Sent: Wednesday, December 10, 2003 3:33 AM
> > > > > To: AccessD at databaseadvisors.com
> > > > > Subject: RE: [AccessD] matching field error
> > > > >
> > > > >
> > > > > Hello Andy,
> > > > >
> > > > > In the help function i saw what the error means. But it
> > > > made no sence
> > > > > to me. You say: "Is there any way they could have zeroes or
> > > > > zero-length strings rather than nulls". When a field is
> > > > empty i think
> > > > > there is nothing in it. How can it be that a field is empty
> > > > but a zero
> > > >
> > > > > is present??
> > > > >
> > > > > Pedro
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > In antwoord op:
> > > > >
> > > > > > From: "Andy Lacey" <andy at minstersystems.co.uk>
> > > > > > To: "'Access Developers discussion and problem solving'"
> > > > > > Date: Wed, 10 Dec 2003 09:10:22 -0000
> > > > > > Subject: RE: [AccessD] matching field error
> > > > > >
> > > > > >
> > > > > > Pedro
> > > > > > The implication is that the you have Relationships
> > defined with
> > > > > > referential integrity. You are saving a record with a
> > > > test id which
> > > > > > doesn't match to a key value in the tblTest table. The
> > > > odd thing is
> > > > > > that this shouldn't occur if the fields are Null. Is
> > > > there any way
> > > > > > they could have zeroes or zero-length strings rather
> > tha nulls,
> > > > > > because that would do it.
> > > > > >
> > > > > > Andy Lacey
> > > > > > http://www.minstersystems.co.uk
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: accessd-bounces at databaseadvisors.com
> > > > > > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > > > > > > Pedro Janssen
> > > > > > > Sent: 09 December 2003 22:41
> > > > > > > To: AccessD at databaseadvisors.com
> > > > > > > Subject: [AccessD] matching field error
> > > > > > >
> > > > > > >
> > > > > > > Hello Group,
> > > > > > >
> > > > > > > i get the following error in a form, when i close it
> > > > and the field
> > > >
> > > > > > > 'PrTestID' is empty:
> > > > > > >
> > > > > > > The microsoft Jet database engine cannot find a record in
> > > > > > > table 'tblTest' with key matching field(s) 'PrTestID'
> > > > > > >
> > > > > > >
> > > > > > > How is this possible, because the field isn't required?
> > > > Al the ID
> > > > > > > fields in the form give the same error when they are empty
> > > > > > > (and all aren't reqiured).
> > > > > > >
> > > > > > >
> > > > > > >
> > >
> > >
> > > _______________________________________________
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> > >
> >
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/a> ccessd
> > Website:
> > http://www.databaseadvisors.com
> >
> >
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

________________________________________________
Message sent using UebiMiau 2.7.2



More information about the AccessD mailing list