Custom Settings Worksheet
Attached is an example of a custom Settings Worksheet.
CPerry, you need to start work on this ASAP. It's holding me up.
Afterwards, you can make the sheet pretty and pleasing an easy for the User to understand and use. (You might sell this, who knows. Plan ahead and be prepared.)
You will need all three Hats to work on this
The developer, (you in your Developers Hat,) in consultation with the User, (you in your User's Hat,) will decide what goes in the User Columns on the sheet
The Developer, checking with Bet Angel's Documentation, decides what BA addresses go in the Input Addresses Columns.
For testing, The Developer or Coder decides what goes in the Helper Output Addresses. The User, consulting with the Developer, makes those decisions after the APP is in production
The Developer, in consultation with the Coder(s,) (that is you in your Coder's Hat and me,) decide what Name to put in the Developer's Column.
For now, don't worry about how the code will interact with this sheet, I got that ATT.
Well thought out Variable Names are a very important part of good Coding, one that is ignored by all amateur and many professional coders. Please. before you start, review all the code samples I have provided and get a good feel for how I name variables.
Q&A: No. I don't think Hungarian Notation is applicable to VBA. Hungarian, AKA, Reverse Polish Notation or RPN, was created for code that might contain one or more "Modules" or Procedures many thousands of lines long written in C or ADA. VBA Coders rarely see even 100 line long Procedures, and Modules are usually broken down into manageable chunks.
Compare:
RPN
Code:
sEmpNm As String
iEmpAg As Integer
dtEmpBrth As Date
VBa
Code:
EmployeeName As String
EmplyeeAge As Integer
EmployeeBirthDate As Date