Eric, <Let's say I have a Database called Neighborhood. Under this database I have a table called Dog. My Dog table has a column called Bark. Bark is defined as CHAR(3) and consists of YES/NO. I have a second table called Tree. My tree table needs a column called Bark, which should consist of data describing the bark of my particular tree (to decided what affects the dog's urine may have on it), but I cannot do that because Rbase will only let me have a CHAR(3) column for Bark. I should not be required to name my column TreeBark, or DogBark as they are already described by the tables they are in. In response to your Water/Oil example, if you tried to perform functions cross referencing a Dog.Bark and a Tree.Bark, you have problems elsewhere.>
"The term " bark" is used most often in a nontechnical context and refers to all tissues external to the vascular cambium (Srivastava 1964, Esau 1965). Accordingly, the bark is an aggregation of organs and tissues that includes phloem and secondarily thickened tissues from the secondary plant body, as well as epidermis, cortex and phloem derived from the primary plant body (Esau 1965). The term bark was used by earlier authors in a technical context in reference to all dead tissues exterior to a deep-seated periderm (de Bary 1884, B�sgen and M�nch 1929). Contemporary authors refer to this aggregate of dead tissues, which consists of alternating layers of periderms and associated tissues, as "rhytidome", a term often considered synonymous with the term "outer bark" (Eames and MacDaniels 1947, Esau 1965). The living organs of the bark consist of the phloem and the living tissues of the innermost periderm, the phellogen and phelloderm. All living tissues have been collectively termed the "inner bark" (Eames and MacDaniels 1947). Borger (1973) provided an excellent discussion of the development and shedding of characteristic bark types. Trockenbrodt (1990) has provided an informative survey and discussion of terminology used in the bark anatomy literature." I would use these column names instead (you can use other name to archive the same thing) Tree_Bark = Rhytidome or Vascular_cambium or outer_bark or inter_bark <And I cannot believe that you are making the statement that SQL Server is not an RDBMS. That hints to me you are prejudiced towards your old ways and tools, and unable to comprehend the glorious, illustrious, object orientated, client server wonder... <trumpet please> SQL SERVER.> Purchase that package and do your application! I'll be done weeks before you are! And I've spent a lot less money! < Hey candles worked fined, why bother with electricity? > I would rather use oil lambs or natural gas! They have better lighting properties than candles! Your Bark issue is a good example (narrow view of the hold database) to present your case of WHAT IF but to me it would be poor design of a database and it's information needs! I would not use a column to identify if a tree has bark or not (the yes/no) but to select from a list of options of what type (a characteristic) of the bark it has and one of those selections would be none!!!! "mierda la toro" Oma ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
