Stuart McLachlan
stuart at lexacorp.com.pg
Sun May 13 16:48:26 CDT 2012
To answer your first question - because this way you only have to do it once. Take an invoice line for example. You need to store Qty, UnitPrice, IsTaxable. Rather than having to create a LineTotal function on every form and report or a calcuated field in every query you use, you can just create a calculated field once in the table and use it where required. You are effectively removing business login from the UI to the data level. It's the same reason you embed business logic in SQL Server stored procedures rather than in the UI. It's not about what the "user" thinks. The "user" shouldn't know anything about the way data is stored or calculated. It is an additional programmer tool. -- Stuart On 13 May 2012 at 8:07, Charlotte Foust wrote: > Maybe I"m missing something here, but why on earth don't you simply do this > in code or in a query? If the data doesn't change, there's no reason to > build it into the table. If the data does change, it should do so through a > user interface which can contain code or macros to run a query. If the > user just thinks calculated columns are the newest miracle and wants them > for that reason, gently explain to him/her that just because you > theoretically can do something doesn't mean you must. If that doesn't > work, hit the client gently over the head with a large hammer! > > Charlotte Foust > > On Sat, May 12, 2012 at 10:46 AM, Mark Simms <marksimms at verizon.net> wrote: > > > It keeps getting better. I tried to change the data type from Double to > > Currency. > > It accepted it. When I tried to open the table again, I got an error > > "Property Not Accepted". > > I performed a compact and repair....and the table disappeared ! > > > > The reason I needed to do this is that a custom filter : [column] <> 1 > > would > > fail for dbDouble. I guess I could have changed the Expression and wrapped > > the 3 thousand characters in Round(), but then again, maybe that wasn't > > supported. > > > > > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > > > > > Website: http://www.databaseadvisors.com > > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >