Subdatasheet Name, What is this?

  • Thread starter Thread starter Denise
  • Start date Start date
D

Denise

MVP's have recommended setting this property in the table to NONE.
I can't find info on what this setting does and what happens when [Auto] or
[None].

Please explain.
Thanks.
 
MVP's have recommended setting this property in the table to NONE.
I can't find info on what this setting does and what happens when [Auto] or
[None].

Please explain.
Thanks.

A "Subdatasheet" is a misfeature (for many of us) introduced in A2002. It lets
the user view a Datasheet view of a parent table, and when they select a
record on the datasheet, a subdatasheet shows up below that line showing at
least some rows from a child table related to the main parent table. The
[None] setting disables this; selecting a specific table name causes that
table to be displayed in the subdatasheet; [Auto] evidently gives Access carte
blanche to display whichever child table it considers appropriate.

In practice, the subdatasheet feature does two things: it encourages the
misuse of table datasheets for interaction with data, rather than the proper
use of Forms and Subforms; and it can cause dramatic degradation of
performance.
 
Now I understand. I never liked or used that feature. I've turned off.

John W. Vinson said:
MVP's have recommended setting this property in the table to NONE.
I can't find info on what this setting does and what happens when [Auto] or
[None].

Please explain.
Thanks.

A "Subdatasheet" is a misfeature (for many of us) introduced in A2002. It lets
the user view a Datasheet view of a parent table, and when they select a
record on the datasheet, a subdatasheet shows up below that line showing at
least some rows from a child table related to the main parent table. The
[None] setting disables this; selecting a specific table name causes that
table to be displayed in the subdatasheet; [Auto] evidently gives Access carte
blanche to display whichever child table it considers appropriate.

In practice, the subdatasheet feature does two things: it encourages the
misuse of table datasheets for interaction with data, rather than the proper
use of Forms and Subforms; and it can cause dramatic degradation of
performance.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top