Re: Creating a key on the Input form
- From: "Larry Daugherty" <Larry.NoSpam.Daugherty@xxxxxxxxxxx>
- Date: Thu, 17 Nov 2005 07:37:32 -0800
Not sure I understand your issue as your thread doesn't define it at
the outset. However, I believe your problem would be solved by
including BOTH fields in the Primary Key OR by using an Autonumber for
the Primary Key.
HTH
--
-Larry-
--
"SharonInGa" <SharonInGa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BAD32875-509F-41A1-8E6E-C41DA146BEA8@xxxxxxxxxxxxxxxx
> The selection of one of these fields creates the key field. This
field
> inputs into a table with a mahy to many relationship. A customer
may have a
> PO# or a BOL# or both. A PO# takes priority over a BOL#. The
process works
> great if you are in the record only once. However, an error message
appears
> saying that there is a problem with the field relationship if you go
back
> into the record for whatever reason. What event should this code go
in or
> what can I do differently?
>
> fieldOne, fieldTwo, BOL#, POL#, (Invisible) KeyField
>
>
> Private Sub PO__LostFocus()
> If Me.BOL_ > 1 Then
> Me.MerchandisePO_ = Me.BOL_
> Else
> End If
>
> If Me.PO_ > 1 Then
> Me.MerchandisePO_ = Me.PO_
> End If
>
> End Sub
>
.
- Prev by Date: Re: automating outlook via access
- Next by Date: Re: Clicking several records for detail
- Previous by thread: Re: automating outlook via access
- Next by thread: Re: Clicking several records for detail
- Index(es):
Relevant Pages
|