I understand what you are talking about, and even grumbled about it while I was doing it. I was using this explicitly as an excuse to start messing with tables since I hadn't previously ever done so. As a result, most everything else is referenced to the table. The stuff presently using ranges is basically what I wasn't able to figure out how to do through the table itself.
As for future use, the sheet as you have it in front of you is entirely "finished" and functional other than this listbox issue and a few minor userform behaviors. 99% of the roughly 200 tools we have run less than a dozen parts, and there's only 1-2 which need any significant number of columns so I don't need anything additional added which would increase complexity, as you stated.
I attempted to insert that and stop using the table but after the 5th error that required switching to ranges I tried just using it on its own with the table and have a type mismatch here. Yes I understand you requested to not use said table and that might be related.
I went back and renamed my previous uses of x to xV but that solved nothing.
Is there any way I can utilize that without needing to rework every other reference to the table in the project?
I am objectively terrible with VBA but sadly its the only "approved" option I have for the time being.
Basically, I create something like this and pester everyone to use it a few times in read only mode and eventually I manage to make the case to pay to get it built into our existing ERP database.
For now, my work day is finished, but I appreciate the response.
Bookmarks