Solved Replicate Text Box in Continuous Form

[theDBguy]

I'm storing em in the table and I'm quoting ur words " especially if there are financial consequences for using them "

At the end of the month, there's a report that calculates total hours of lates per employee !! that's why I'm storing em !!
Please tell me your concerns in details

Hi. What I am saying is if you store a calculated value, like HoursWorked and later use it to determine how much to pay an employee, you run the risk of incorrectly paying them, if the data in HoursWorked is inaccurate, which could happen if either or both the ClockIn or ClockOut data was later changed/updated, without also updating the HoursWorked value. But by just "calculating" this value on the fly (instead of storing it, then you can be sure your employee is paid correctly every time.

In other words, if you're using something like this:

HoursWorked * PayRate = EmployeePay

I am saying this is better and more accurate:

(ClockOut-ClockIn) * PayRate = EmployeePay

Does that make sense?

 

[alvingenius]

Hi. What I am saying is if you store a calculated value, like HoursWorked and later use it to determine how much to pay an employee, you run the risk of incorrectly paying them, if the data in HoursWorked is inaccurate, which could happen if either or both the ClockIn or ClockOut data was later changed/updated, without also updating the HoursWorked value. But by just "calculating" this value on the fly (instead of storing it, then you can be sure your employee is paid correctly every time.

In other words, if you're using something like this:

HoursWorked * PayRate = EmployeePay

I am saying this is better and more accurate:

(ClockOut-ClockIn) * PayRate = EmployeePay

Does that make sense?

i got your point.
But in my situation, I only calculate Late time form ClockIn, and clock-in is not editable in form, it got the value from update query that gets the clock-in from another DB storing attendance time from attendance machine . so i'm not afraid of change/update the clockin .

 

[theDBguy]

i got your point.
But in my situation, I only calculate Late time form ClockIn, and clock-in is not editable in form, it got the value from update query that gets the clock-in from another DB storing attendance time from attendance machine . so i'm not afraid of change/update the clockin .

Hi. All I am trying to make you aware was there is always a risk with storing calculated values. But, as long as you accept that "risk," you decide what to do with it. As for me, I don't see any benefit with taking that risk when calculating the value "on-the-fly" is more accurate and reliable. Good luck!

 

[zeroaccess]

What happens if employee time needs to be updated/modified? That happens all the time with timekeeping. Your stored values would be wrong.

 

[alvingenius]

What happens if employee time needs to be updated/modified? That happens all the time with timekeeping. Your stored values would be wrong.

employee time is not changeable or editable at all!

 

[theDBguy]

employee time is not changeable or editable at all!

On the form, or in the table? How does your auditing process work?

 

[alvingenius]

On the form, or in the table? How does your auditing process work?

it's attendance time !!! I get the time from Attendance Software with update query to attendance table, so in form time is not editable.

 

[theDBguy]

it's attendance time !!! I get the time from Attendance Software with update query to attendance table, so in form time is not editable.

And the attendance software will "never" change those times after the fact? Just playing Devil's Advocate here...