Access JumpStart 2.0 | Blog

A Rapid Development Framework for Microsoft Access

I am pivoting directions on a project. After producing what the customer asked for, he realized it was making the whole system more complicated than he wanted, but may want to revisit it in the future. Thankfully, since I use versioning, it was trivial to move back to a desired point in the code that would allow me to retain the needed portions of the changes and continue moving in a new direction.

In this case it was a desire to separate rows that were related in counting up the same type of thing, but with different SKUs. Originally the customer wanted to be able to see a productivity number for hours worked on that SKU verses widgets produced. But then later decided that he only needed to track the hours on a particular set of SKUs.

We are pivoting so that instead of every SKU being separated out and tracked hourly, they all remain grouped unless a checkbox for that SKU is checked, in which case it will be removed from the total quantity, but split out into it’s own line but without any hours for that SKU.

In any case, having the version control system makes changes to the system like this much more palateable for the whole team, customer and developer alike.

Sign up For a Daily Email Adventure in Microsoft Access

Every business day (typically M-F), I'll send you an email with information about my ongoing journey as an advanced Access application developer. It will be loaded with my tips and musings.

    We won't send you spam. Unsubscribe at any time.