[AccessD] Calculated Fields

[Stuart McLachlan]

>From https://msdn.microsoft.com/en-us/library/office/ff945943%28v=office.14%29.aspx

"There are those who would argue that adding calculated fields in a table violates rules of 
normalization, and in some cases, they are right. In some cases, it is worth breaking the 
rules: If you know that you will need the calculation in every object based on the table, if you 
know that the expression cannot change over time, or if having the calculation in the table 
would make your data clearer, then use the feature. You can always, as in Access 2003 or 
Access 2007, include calculations in queries, also. Doing so requires you to base all forms 
and reports on the query, instead of on the table-end-users may miss this important point, so 
if end-users are creating their own forms and reports, it is best to consider using calculated 
fields in tables.

Be aware that calculated fields cannot call user-defined functions, only built-in functions. In 
addition, you must supply all parameters for methods that you call, even if the parameters are 
optional.

If you use calculated fields, be aware that earlier versions of Access will be unable to open 
the table-verify that you will need the table only in Access 2010 before you use this new 
feature."


-- 
Stuart

On 15 Jun 2015 at 16:58, Charlotte Foust wrote:

> I haven't built a web app, so I can't speak from experience.  That's
> my perception of them, but I haven't used them so don't count on my
> uninformed opinion.  I do know I haven't seen one used in any of the
> pro apps I seen presented at conferences, etc.
> 
> Charlotte Foust
> (916) 206-4336
> 
> On Mon, Jun 15, 2015 at 4:40 PM, Susan Harkins <ssharkins at gmail.com>
> wrote:
> 
> > So, you think calculated fields are of the same ilk? A column that
> > updates while someone's updating a table via a web app?
> >
> > Susan H.
> >
> > On Mon, Jun 15, 2015 at 6:59 PM, Charlotte Foust <
> > charlotte.foust at gmail.com>
> > wrote:
> >
> > > Web-based solutions are really what data macros were created for,
> > > to replace the VBA and Access macros that don't work on the web. 
> > > I've been hearing this from MVPs for some time but I can't point
> > > to a particular article.
> > >
> > > Data macros can be very powerful but, like triggers, they can be
> > > used inappropriately too.  I tend to use them to put date/time and
> > > user ID
> > into
> > > records automagically, but I don't use them to update a totals
> > > value.  I don't think they work across tables, either, which
> > > triggers can.
> > >
> > > Charlotte Foust
> > > (916) 206-4336
> > >
> > > On Mon, Jun 15, 2015 at 3:51 PM, Susan Harkins
> > > <ssharkins at gmail.com> wrote:
> > >
> > > > Good information -- can you expound? Not necessary, but I'm
> > > > interested
> > in
> > > > following this comment.
> > > >
> > > > Susan H.
> > > >
> > > > Their use in Access is, I think, aimed at web-based
> > > > > solutions.
> > > > >
> > > > >
> > > > --
> > > > 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
> > >
> > --
> > 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
>