A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data
I think you are just saying that you ignored it in regards to the current code that you wrote and I would need to add it in myself.
Tim,
That is correct. IMHO the first step for you is to understand how my code works.
And especially what happens if things goes wrong.
An invoice means a clear structure for you and me, but for VBA in Excel there are just cells anywhere which can contain anything! There are soo many scenarios where a simple typo can mess up everything.
So after you made your positive tests with valid input, try to make the code fail!
A good code should catch all invalid input and throw a meaningful error message for the end user. The end user should never see "Enter debug mode?" nor that the VBA editor opens and the code stops anywhere. That's the worst case scenario from my point of view.
Have a nice weekend, if you have further questions, I'll be back on Monday.
Andreas.