Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Data question
2 views
Skip to first unread message
Eric Brenner
Oct 21, 2011, 11:33:25 AM10/21/11
to
Simple question.
I have a Inventory Database that I am making updates to. One of the
requirements is that they want to calculate a labor charge based on
our company's standard labor rate. Instead of hard-coding this into a
function, I would like to have this accessable to certain individuals
that have authority to change this. Should I store this value in a
table, a text file, somewhere else?
Your opinions are greatly appreciated!
Eric
I have a Inventory Database that I am making updates to. One of the
requirements is that they want to calculate a labor charge based on
our company's standard labor rate. Instead of hard-coding this into a
function, I would like to have this accessable to certain individuals
that have authority to change this. Should I store this value in a
table, a text file, somewhere else?
Your opinions are greatly appreciated!
Eric
Tony Toews
Oct 22, 2011, 8:46:15 PM10/22/11
to
On Fri, 21 Oct 2011 08:33:25 -0700 (PDT), Eric Brenner
<ebrenn...@gmail.com> wrote:
>I have a Inventory Database that I am making updates to. One of the
>requirements is that they want to calculate a labor charge based on
>our company's standard labor rate. Instead of hard-coding this into a
>function, I would like to have this accessable to certain individuals
>that have authority to change this. Should I store this value in a
>table, a text file, somewhere else?
You should store this in a table with a start and end date.
<ebrenn...@gmail.com> wrote:
>I have a Inventory Database that I am making updates to. One of the
>requirements is that they want to calculate a labor charge based on
>our company's standard labor rate. Instead of hard-coding this into a
>function, I would like to have this accessable to certain individuals
>that have authority to change this. Should I store this value in a
>table, a text file, somewhere else?
You will then either want to
1) have multiple records in this table so you can lookup the labour
charge rate as required.
2) store the labour rate with each transaction so you can retrieve the
proper rate in future years.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
0 new messages