So easy I Think

  • Thread starter Afrosheen via AccessMonster.com
  • Start date
A

Afrosheen via AccessMonster.com

Thanks again for reading my post.
What I'm trying to do is to keep a running total.

Because of the cut backs everyone is facing my employer wants us to take a
furlough. So, what I'm trying to do is to find a way where I can enter the
amount of time used then deduct it from the time given/balance

I have 3 fields I'm using
Fhours, Used, Balance.

The Fhours is a one time entry. So I guess you'd have to subtract the used
from the balance. The problem is that it doesn't. What happens is that it
just takes the used and then subtracts from the current balance not the
balance from the previous record.

This is what I have on the Afterupdate() on the used:
If Earned > 0 Then
Bal = Earned - Used
Else
Bal = Used - Bal
End If

Thanks for your help.
 
T

ThriftyFinanceGirl

Sounds like you are trying to use a table like a spreadsheet....

Your table should only have one field in your scenario (but you need a
primary key too) and that field is the hours worked.

Then you create either a form or a report and do your calculations there...
You should never really store a calculated field in a database (Because you
can calculate it anytime you need it) except under certain circumstances.

For your small application I would create a spreadsheet. Unless you are
creating this for a large group of workers.
 
A

Afrosheen via AccessMonster.com

Thanks for getting back to me. Yes, to me it is a large group. Almost 1000. I
guess what could happen is that the inputter can manually put in the
information. I really shouldn't be that hard. The problem is you know people,
they input things differently. I'll see what I can do though.

Thanks again.

Any more suggestions though would be appreciated
Sounds like you are trying to use a table like a spreadsheet....

Your table should only have one field in your scenario (but you need a
primary key too) and that field is the hours worked.

Then you create either a form or a report and do your calculations there...
You should never really store a calculated field in a database (Because you
can calculate it anytime you need it) except under certain circumstances.

For your small application I would create a spreadsheet. Unless you are
creating this for a large group of workers.
Thanks again for reading my post.
What I'm trying to do is to keep a running total.
[quoted text clipped - 19 lines]
Thanks for your help.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top