[AccessD] Subdatasheet vs. Relationships?

Well Charles...that is a fine horse you have...highest one I've seen this
week.


Mark



-----Original Message-----
From: Wortz, Charles [mailto:CWortz at tea.state.tx.us] 
Sent: Friday, August 22, 2003 8:20 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Subdatasheet vs. Relationships?


Christopher,

What gives is that you inherited a db from someone that knew nothing about
db design.  My condolences to you.  It may be easier to throw it away and
start from scratch.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us



-----Original Message-----
From: Christopher Hawkins [mailto:clh at christopherhawkins.com] 
Sent: Thursday 2003 Aug 21 16:01
To: accessd at databaseadvisors.com
Subject: [AccessD] Subdatasheet vs. Relationships?

I have inherited an A2K database that has numerous tables related to one
another via the SubDatasheet property. Make no mistake, I hate this feature
with a passion because it slows databases down. 
However, if there is a legitimate reason to use it I'll buy in.

The db has no relationships defined in relationships view. In the mdb is a
main form based on a single table (no JOINS in the RecordSource), with
several subforms on tabs. Each subform is getting data from a single,
distinct tables (that is, no two subforms use the same table for data. All
subforms are linked to the main form by BlahID.

Now, for the life of me, I can't figure out what using the SubDataSheet
property of the tables does to help this application. 
What gives?

-Christopher- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com