No worries Duritz.

The method you have described, I have been there and done that, so to speak. Although I have not had to use Access, I found another database at the time was a bit easier to work with.

The point is this,Excel and Database (Any) is a very good way to use as proto-type, and it can remain as your "program" if it works for you, good !
From there though, I found there were requirements to enhance the system for it to do more. Meaning, everything Excel and a Database was already doing would then be replicated by developing a program.

I am sure when you get to the end of your current cycle of methods ( I know it can become tedious), the "logic" then will possibly direct you "program.exe" development.

If or when you do, and do some interim cost findings to have it developed, the costs are astounding in real dollar terms. This is ok to.
Programmers are like people, they need to eat,wash,pay the bills just the same as everyone else !
My quote was much more than the figure I posted when I got to this stage. ( No, I did not pay to have it done, incase anyone is wondering,but we done our homework prior.)

In hindsight, I would have intergrated some of the Database with the Database develoment package provided with RB. But RB was not up to it then, it is now with the latest version.
Once you do ever get to this stage and once you do have your "program.exe" (for lack of better terms), it's another "dimension".

Good luck with your projects.