Calculated Field

[Dave]

I am trying to build a table of Inventory Items including
such things as Purchase Cost and various conversion
factors to allow a Unit Cost to be calculated. For
example, if I purchase an item for $120 per case with 10
items per case the Unit Cost would be $12.

I would like to store the Unit Cost in the Inventory
table. Access will not allow me to create a "calculated"
field in a table. I believe I could use an update query
to update a numeric field, but that query would need to be
run each time any item is updated. Controlling that would
probably be a nightmare.

I am not an Access expert, but is there a way that the
Unit Cost can be calculated and stored in the table when
an item is added or changed?

Thanks.

 

[Lynn Trapp]

It's not likely that you really need to store the value. Just do the
calculation in a query when you need it.

 

[Dave]

Thanks for the response. It just confirms that Microsoft
is trying to control how I do things instead of letting me
do them the way I want to. If I want to store the value,
I should be able to. No other database program I have
used in 20 years has this restriction. [Nothing against
you, Lynn. I am just disappointed that I am forced into
using such limited software.]

 

[Tim Ferguson]

If I want to store the value,
I should be able to. No other database program I have
used in 20 years has this restriction. [Nothing against
you, Lynn. I am just disappointed that I am forced into
using such limited software.]

I am by no means an apologist for Microsoft, but this time they are doing
things The Right Way. The last forty years of math theory is against you, I
am afraid -- check out any basic text on Relational Theory and database
design.

PEBCAK...


B Wishes


Tim F

 

[Lynn Trapp]

Dave,
I'm sorry you feel that way but, as Tim F. has pointed out, this is not
Microsoft's doing, but based totally in the theory of relational database
design. I don't know what database programs you may have used in the past
but I don't know of any that are designed to store calculated values at a
table level, except for historical purposes.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

Thanks for the response. It just confirms that Microsoft
is trying to control how I do things instead of letting me
do them the way I want to. If I want to store the value,
I should be able to. No other database program I have
used in 20 years has this restriction. [Nothing against
you, Lynn. I am just disappointed that I am forced into
using such limited software.]

-----Original Message-----
It's not likely that you really need to store the value. Just do the
calculation in a query when you need it.



--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm





.

 

[Jeff Boyce]

Dave

Consider re-reading Lynn's comment -- he didn't say you couldn't, he said
you probably don't actually need to...