>> 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) << >> 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. <<
I can easily see situations why I would want to do consolidations on a table that has information on my dogs and their relationships to the trees, based on your description. That you foresee no possibility does not mean that it is not there. On the other hand, in such a case, even if Rbase allowed it, I would NOT name the columns as you suggest. I would use something like TreeBark and Barks to differentiate two very different types of information. Given the nature of the database you are likely to wind up with, you may very well have a situation where seeing "barK" (or t1.bark) is not going to immediately tell you which field you have there. ================================================ 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
