Yes, the original was just a sample.



They do look at this, thus I have additional columns that summarize the data.

I am a former data administrator (retired), and am creating this for a friend who needs the data for employee evaluations. They spent a chunk of change on a check_in system that uses a key fob that transmits when they pass the station, as the employees are spread out and it is imperative that everyone be at their duty station on time.

Since my last post, I went ahead and tried the Table option for the Data Table, and that helped a lot. I also changed the calculation to Manual so that I wouldn't have to wait.

I have thought of converting the formulas to values, but since I'm not the one who is actually going to be managing this, I had not done that yet (I actually only have a portion of the data). I think that is a good idea though, and I think they only pull the data from the system at the end of the month, so that could be part of their process.

They get the data report from the system in an Excel doc, so they could append the data, calculate, then convert to values, and the summary columns would automatically calculate without any problem.

I dabbled in VBA, but it has been quite a while.

This may just be the best way to approach this so I can hand it off.

Thanks again!

Changing the calculation to Manual is another good idea, IMO; I didn't think of that, but it means you can decide when you want to go through the wait, even after you've reduced it.

If you're thinking VBA may be the best way so you can then hand it off, I'm inclined to disagree. I love VBA automation, but once I hand something off I want the victim of my work to be able to deal with it himself if it breaks; so VBA is a good idea only if there's someone there who can fix broken VBA. I'm guessing that isn't the "this" you were referring to, but I mention it just in case I'm mistaken.