Sami We all have diffrent logic on this. I am surprised that I could execute the file. I would have expected an error on the second compute.
If I do it from RBDESIGN when I put the computed column in the second table it forces to Col1 + Col2. So I am surprised but stay happy since ACCESS is much worse they allow a lot more like defining Col1 as as text in one table and date in next table and integr in third table. Anyway I would regard as a bug! Gunnar Ekblad -----Ursprungligt meddelande----- Fr�n: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] F�r Sami Aaron Skickat: den 24 augusti 2004 17:52 Till: RBG7-L Mailing List �mne: [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
