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

Topic

New Reply

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.

Reply | Quote

Replies

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.

Reply | Quote

[indent]

---

You can’t create a new record without the key field.

---

[/indent]

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.

Reply | Quote