Jim I agree with you that having positionally-dependent multivalues is often a poor design, but what exactly is wrong with having multivalued phone numbers with an associated phone type? Surely that's an appropriate use of an NR model and why WHEN clauses were invented. It's no different from how you would store it in a relational format, with the benefits of the loss of the extra table and foreign key columns (and the indexing and obvious join and transaction overheads...)
But there is a more general point: I've never come across a good publication or course that taught how to design a multivalue database. Plenty on how to code one up, administer one, use the various languages etc. but nothing that dealt with the first principles of design. Perhaps it's the assumption that everyone in the field is migrating from some previous multivalue incarnation or working on some kind of legacy application.. but they all seem to assume that you want to build a house without laying the foundations. Brian On Jun 26, 8:38 pm, "Jim Idle" <[email protected]> wrote: > You need to read the knowledgebase but need more fundamental training. For a > start though, tell whoever told you that phone number should be a multivalue > field that they need some training ;-) Ask your supplier for some training > options. > > Jim -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
