Please review
Before Posting (VBA or SQL) Code.
@rekedtechie
I have to disagree strongly with your analysis. Anything other than a table to store the information would be wholly inappropriate and would fail to manage and reflect previous usage. Managing the entries used only in the current session would be pointless, as the data across that session wouldn't even start to be worth the effort.
I can't say too much about the code except that we like compiled code here for good reason. Such code that is uncompiled and uncompilable tends only to mislead users. Even looking at it as pseudo-code I fail to see how it can be considered even as illustrating the fundamental logic required for this question. The obvious omission of any event procedures indicates clearly it cannot correctly handle the problem raised.
I'm not here to have a go at your code. I just felt it was important not to allow the idea that it is a viable solution to go unchallenged, as it misleads those less experienced and less capable members into following a dead-end path.