Sami: I have noticed the same thing. My memory is fuzzy on this but I seem to remember that the old DOS versions would bring the definition when you entered a computed column name...but again, I could be wrong on this as my memory is not as good as it used to be...old age <g> I agree with you that the data dictionary should check for consistency but I am open to reasons why it should not. I am going to guess that it has stayed this way as a legacy standard; I suspect that if the Data Dictionary is changed to check (and enforce) the definition of computed columns, there may be a whole lot of older databases that would suddenly sprout errors, no? A compromise would be to have the Data Dictionary bring up the definition when adding columns to a table in the Designer, but allow the user to override the definition without further checks. Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ====================================================== -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sami Aaron Sent: Tuesday, August 24, 2004 10:52 AM To: RBG7-L Mailing List Subject: [RBG7-L] - Computed columns - different expressions Hmmm ... I just submitted this as a bug - two different tables, same column names but the computed columns have different expressions. CREATE TABLE `Computed1` + (`col1` INTEGER , + `col2` INTEGER , + `col3` INTEGER , + `colComputed`= + (col1+ col2) INTEGER ) CREATE TABLE `Computed2` + (`col1` INTEGER , + `col2` INTEGER , + `col3` INTEGER , + `colComputed`= + (col2+ col3) INTEGER ) The RDCC response is that it was that way in 6.5++ - which is true so it won't be treated as a bug. But why do I think it shouldn't be that way? I always was under the impression that the R:BASE engine was set up to prevent this. I'd be interested in other's opinions on this as to why it's NOT that way or why it SHOULDN'T be that way. Sami ------------------------------------------ Sami Aaron Software Management Specialists 19312 W 63rd Terr Shawnee KS 66218 913-915-1971 mailto:[EMAIL PROTECTED] www.softwaremgmt.com
