Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
Computed column with external constants |
Mon, Aug 31 2009 10:05 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | I'm just starting work on my revised app for diabetes monitoring. One of the things to monitor is flab. My current system calculates BMI (and yes I know some parts of the medical fraternity now discount it) and stores it. I thought this would be a nice use of a computed column BUT I need to access an external variable (height) which will not be stored in the database.
Suggestions please. Roy Lambert |
Mon, Aug 31 2009 3:04 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I'm just starting work on my revised app for diabetes monitoring. One of the things to monitor is flab. My current system calculates BMI (and yes I know some parts of the medical fraternity now discount it) and stores it. I thought this would be a nice use of a computed column BUT I need to access an external variable (height) which will not be stored in the database. >> In which table is this computed column located ? Is there any reason why you don't want to put the height in the same table ? -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Sep 1 2009 3:39 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
The computed column is in table BodySize not that I can see that helping <vbg>. I have two reasons for not wanting to put the height into the table. Firstly this is a single user app so there should only be one instance of height and I hate duplicating data in a wasteful way. Secondly if someone makes a mistake (I thought I was 6'5" but realised I'm only 5'6") having it recorded means having to change all the records. Roy Lambert |
Tue, Sep 1 2009 12:03 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< The computed column is in table BodySize not that I can see that helping <vbg>. >> Well, height would seem to be something that should go in the BodySize table. << I have two reasons for not wanting to put the height into the table. Firstly this is a single user app so there should only be one instance of height and I hate duplicating data in a wasteful way. Secondly if someone makes a mistake (I thought I was 6'5" but realised I'm only 5'6") having it recorded means having to change all the records. >> So you're already storing the height, just in another table ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Sep 2 2009 3:27 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
><< The computed column is in table BodySize not that I can see that >helping <vbg>. >> > >Well, height would seem to be something that should go in the BodySize >table. It was going to be called flab but I chickened out ><< I have two reasons for not wanting to put the height into the table. >Firstly this is a single user app so there should only be one instance of >height and I hate duplicating data in a wasteful way. Secondly if someone >makes a mistake (I thought I was 6'5" but realised I'm only 5'6") having it >recorded means having to change all the records. >> > >So you're already storing the height, just in another table ? In an .ini file Roy Lambert |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |