4 ms·
Due to system limitations, I made a stats tracker for my team in AccessDB. Due to the awfulness of access, I made an excel&vba front-end that would push data to
by BariumBlue 8y ago
Due to system limitations, I made a stats tracker for my team in AccessDB.
Due to the awfulness of access, I made an excel&vba front-end that would push data to and pull data from access.
It's been working surprisingly well so far, with no reported issues
- bhandziuk 8y agoI'm curious what you found to be the brickwall for you when using Access?
- BariumBlue 8y agoThe existing "solution" was a gigantic excel where people would put it times and names. In Access, when you enter times, you have to use a specific format, (the datetime group specified by the Windows default) rather than just "23:40" or w/e. I've seen a hack where the hour and minutes are separate boxes, but it wasn't pretty. Just this issue was enough to make Access unappealing. Access's interface is a bit unintuitive, and given that most people I worked with weren't particularly technically capable, I preferred to present them with the familiar Excel interface (and a few extra buttons), rather than teach them an application they've never used before. Plus, the existing workflow already used Excel, so I hijacked their workflow and their routine wouldn't be modified much at all (introducing a completely new system would cause a lot of friction and pushback, but one or two extra buttons was fine).
- bhandziuk 8y agoHuh. Next time you can set the date format to "mm/dd/yyyy hh:nn" and you can enter 24 hour times with a date. But I understand wanting to not disrupt an existing workflow too much.