Hi Everyone

 

This is just a question of best practices a guess...

 

If I have data like supplier information which I need to capture in
MOSS,

do I use normal database design principles to outline the columns and
types within MOSS or

do I just add the required fields into one list or content type?

 

Example:

A supplier has name, telno, address ect.

But also has Contacts associated to them.

 

With normal database design you will separate the two because it has a
one to many relationship between suppliers and supplier contacts.

But in MOSS you may add these contacts with their detail in one multi
line field within the list or content type.

 

Is there any article or blog that discusses this? My personal opinion is
to go with the traditional database design principles.

 

I would really want to know what's been done out there.

 

Regards

Arno


***************************** Disclaimer *****************************

The contents of this electronic message and any attachments are intended only 
for the addressee and may contain privileged or confidential information. They 
may only be used for the purposes for which they were supplied. If you are not 
the addressee, you are notified that any transmission, distribution, 
downloading, printing or photocopying of the contents of this message or 
attachments is strictly prohibited. The privilege of confidentiality attached 
to this message and attachments is not waived, lost or destroyed by reason of 
mistaken delivery to you. If you receive this message in error please notify 
the sender by return e-mail or telephone.

Please note: the Department of Public Works carries out automatic
software scanning, filtering and blocking of E-mails and attachments (including 
emails of a
personal nature) for detection of viruses, malicious code, SPAM, executable 
programs or content it deems
unacceptable. All reasonable precautions will be taken to respect the privacy of
individuals as outlined in the DPW Privacy Plan. Personal information will only 
be used for official
purposes, e.g. monitoring Departmental Personnel's compliance with Departmental 
Policies.
Personal information will not be divulged or disclosed to others, unless as 
required by Departmental
Policy and/or State or Commonwealth Law.

Thank you.



------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.

Powered by mailenable.com

Reply via email to