Formula field vs. no formula field
mich_stone_at_yahoo.com
Date: 02/01/05
- Next message: Michael Cheng [MSFT]: "RE: Error message at deployment"
- Previous message: mark baekdal: "RE: Scheduling DB Scripting"
- Next in thread: John Bell: "RE: Formula field vs. no formula field"
- Reply: John Bell: "RE: Formula field vs. no formula field"
- Reply: Tibor Karaszi: "Re: Formula field vs. no formula field"
- Messages sorted by: [ date ] [ thread ]
Date: 31 Jan 2005 22:54:22 -0800
Dear all,
Sounds like a simple question.
I have three fields in my table
FieldA
FieldB
FieldC
FieldD
FieldC = FieldA * FieldB
FieldD = 0.01 * FieldA * FieldB
(actually the scenario is slightly complex that this)
I have two options
1. Declare FieldC and FieldD as formula fields and relax myself by
bothering only about FieldA and FieldB from my asp.net application
2. Worry about updating FieldC and FieldD as "there could be a serious
performance difference"
Updates happen from different screens, and it would make a deal of
difference to me if i can allow sql to take care of the several formula
fields i want to keep. At the same time, i don't want my customers to
come crying saying the system is very slow.
Any advice?
Thanks
- Next message: Michael Cheng [MSFT]: "RE: Error message at deployment"
- Previous message: mark baekdal: "RE: Scheduling DB Scripting"
- Next in thread: John Bell: "RE: Formula field vs. no formula field"
- Reply: John Bell: "RE: Formula field vs. no formula field"
- Reply: Tibor Karaszi: "Re: Formula field vs. no formula field"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|