UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Calculated Field Vs. Query, Any Version    
 
   
NimishParikh
post Oct 4 2019, 10:22 AM
Post#1



Posts: 233
Joined: 30-November 10



Hi Friends,

I have a table with the following fields -

CODE
tblTankColumn
ID, AutoNumber
Project, Text
Tank, Text
ColumnSetID, Number (Integer)
ColumnDescription, Text
ColumnQuantity, Number (Integer)
ColumnPCD, Number (Double)


The angle, two adjacent columns towards the center of the tank, will describe is calculated as 360 / ColumnQuantity. This angle will used many times in the calculations in various queries.

My question is -

Is it worth writing a query that will have all columns from tblTankColum plus a field that calculates DescribedAngle as above OR simply have calculated field in the table itself. Currently I am using query.

Thanks,
Nimish
Go to the top of the page
 
arnelgp
post Oct 4 2019, 10:41 AM
Post#2



Posts: 1,510
Joined: 2-April 09
From: somewhere out there...


Calculated fields are made to make life easy.
there are also calculated fields in mssql.

--------------------
Never stop learning, because life never stops teaching.
Go to the top of the page
 
kfield7
post Oct 4 2019, 12:23 PM
Post#3



Posts: 1,012
Joined: 12-November 03
From: Iowa Lot


While I am not always a purist, a purist would likely point out that:
1. Adding a field to a table requires additional bytes of storage
2. A calculated field does not reflect a normalized table
3. You already have a query that works, why change?
4. With this simple calculation, the calculation time for the query is not significantly different
Go to the top of the page
 


Custom Search


RSSSearch   Top   Lo-Fi    22nd November 2019 - 12:42 AM