If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Database Concepts & Design > SuperType / SubType Question

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-07-04, 21:08
mBlack mBlack is offline
Registered User
 
Join Date: Jan 2004
Posts: 9
SuperType / SubType Question

Hi All,

I know this is a DB specific question but I posted in the Access forum and didnt receive a reply. I hope no one has an issue with this post, if so I will withdraw it.

How does one show SuperType / SubType relationships in MS Access 2000? I need to show the following supertype - tblCollection which is an associative entity containing the common values for the subtypes such as fkValueId for tblValue and fkConditionId for tblCondition. Examples of the subtypes are tblComicBook and tblCoin which each have their own unique values that the other collections do not have. There will be many different types of collections so making tblCollection one big associative entity is not feasable or scalable.

I can do it easily with Oracle designer but I am relativley new at developing with Access.

Any help would be appreciated.

Thanks
mBlack
Reply With Quote
  #2 (permalink)  
Old 11-08-04, 22:36
certus certus is offline
Registered User
 
Join Date: Dec 2003
Location: Canada
Posts: 710
You may try using Oracle designer and generate the DDL. Then use the DDL to guide you as to how to code a generalization hierarchy for access.
__________________
visit: relationary
Reply With Quote
  #3 (permalink)  
Old 11-12-04, 10:14
r123456 r123456 is offline
Registered User
 
Join Date: Sep 2003
Location: The extremely Royal borough of Kensington, London
Posts: 778
I do not believe sub-types are represented explicitly in design view in MS Access, because there are different options to physically represent the implementation. For example:

1) Single table
2) Master + details
3) Collection of detail tables.

Once you have decided on your implementation method, the relationships can then be constructed accordingly.
__________________
Bessie Braddock: Winston, you are drunk!
Churchill: And Madam, you are ugly. And tomorrow, I'll be sober, and you will still be ugly.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On