Subdatasheets and relationships

[albycindy]

Are subdatasheets indicative of working relationships and if so, are they
really important?

All of my tables have subdatasheets (just for my own info so I know whats
going on) but a couple aren't working. Does it show that some of my
relationships aren't right or does it really not matter?

 

[albycindy]

is there someone i can email a pdf of my relationships to for checking? please?

 

[Vincent Johns]

is there someone i can email a pdf of my relationships to for checking? please?

If you can trim down your database (make a copy, remove irrelevant
Tables, delete all but 2 records in each remaining Table, including
everything that might be sensitive, Repair & Compact the database, ZIP
the file, attach the sqeezed-out remains to a message, send it to me),
I'll be happy to look at it when I have time, but not necessarily today.
That way, I can make illustrative changes and send them back. Can't
(easily) do that with a PDF.

They are a convenience. They can be based on whatever matching fields
you have, and it's easy to change from one to another: select "Insert
Subdatasheet" (even though there's already one there) and specify new
linking fields.

If they're not working, I'd be really suspicious that /something/ is not
right!! But, of course, it's possible to use some parts of a database
when other parts are broken.


-- Vincent Johns <[email protected]>
Please feel free to quote anything I say here.

 

[Duane Hookom]

I think I share the opinion of many Access MVPs that subdatasheets are a
mis-feature. Most of us view our table designs and set the subdatasheet
property to none. It is my understanding that subdatasheets decrease
performance.

Viewing and editing of information should be done in forms and reports.

The relationships in your database are a separate issue. If you have some
questions about your table structures, feel free to ask in this NG.

 

[John Vinson]

Are subdatasheets indicative of working relationships and if so, are they
really important?

The Subdatasheets appear if a relationship has been defined.

All of my tables have subdatasheets (just for my own info so I know whats
going on) but a couple aren't working. Does it show that some of my
relationships aren't right or does it really not matter?

"aren't working" isn't very informative, but if you're not seeing the
data you expect then probably either the relationship or the data
itself is wrong. Without seeing more about your tables it's impossible
to guess which!

In my experience, Subdatasheets are *never* essential (they can be
useful for *very* quick and dirty work, but a Form with a Subform
gives the same information in a much better controlled manner); and
they are a MAJOR drag on performance of the database. I routinely set
all Tables' properties from Subdatasheet [Auto] to [None].

John W. Vinson[MVP]

 

[Vincent Johns]

Are subdatasheets indicative of working relationships and if so, are they
really important?

[...]

In my experience, Subdatasheets are *never* essential (they can be
useful for *very* quick and dirty work, but a Form with a Subform
gives the same information in a much better controlled manner); and
they are a MAJOR drag on performance of the database. I routinely set
all Tables' properties from Subdatasheet [Auto] to [None].

John W. Vinson[MVP]

Bearing in mind that mine is very much a minority opinion (I haven't
seen any recent comments agreeing with me), I find subdatasheets, both
in Tables and in Queries, to be very convenient at times, and I think
you shouldn't feel bad about using them. I do agree with John Vinson
that they're never essential.

For that matter, I know people who advocate doing everything in stored
procedures (in Modules, using VBA, and publishing the database in *.MDE
format to hide everything except the Forms and Reports); this, if done
right, will maximize security. They have a point, too, except that
doing this requires a bunch of extra work in developing and maintaining
the database.

Using Tables (with lookup Queries for displaying foreign-key Autonumber
values) and subdatasheets allows me, very quickly, to define an
easy-to-use interface for displaying & updating the data. But I do
avoid inserting subdatasheets into Tables where I don't plan to use them
-- I use them in moderation.


-- Vincent Johns <[email protected]>
Please feel free to quote anything I say here.

 

[John Vinson]

But I do
avoid inserting subdatasheets into Tables where I don't plan to use them
-- I use them in moderation.

Everything should be done in moderation... including moderation!

If it works for you, fine; and yes, I can see that they (and - even -
Lookup Fields) may have their place.


John W. Vinson[MVP]