Results 1 to 3 of 3
  1. #1
    4 Star Lounger
    Join Date
    Dec 2000
    Location
    Faifax, Virginia, USA
    Posts
    542
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Key field on Form Required - why? (A2K 9.0.4402 SR-1)

    In another thread, i mentioned that i wanted to set a subform DefaultValue to the text in a field on the Parent form. In order for this to work, I must include the primary key (an autonumber) from the Parent table.

    Why is the key field required?

    What are the +/- of making this required field invisible? I prefer it invisible because the number is 'meaningless', and would be even more meaningless if it's a GUID.

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Key field on Form Required - why? (A2K 9.0.4402 SR-1)

    You can't create a new record without the key field. Put it on the form, set its visible property to false and move it to the top of the tab order. It will populate itself automatically as soon as you begin entering the subform record. I never make those controls visible, since the user doesn't need to see them.
    Charlotte

  3. #3
    4 Star Lounger
    Join Date
    Dec 2000
    Location
    Faifax, Virginia, USA
    Posts
    542
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Key field on Form Required - why? (A2K 9.0.4402 SR-1)

    <hr>You can't create a new record without the key field.<hr>

    I am curious as to the mechanism.

    Without the key, where does the data go?

    A pointer to a reference or KB article would suffice.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •