Working with Multiple Classes in VBA

[@YvesAustin]

I am starting to dip my toes into class modules. This was a very good video. Thank you Jennifer for taking your time and for not editing the content. It was extremely useful watching the various bumps on the way.

[@oscarrulz6551]

she is an awesome teacher

[@gsr4535]

Enjoy your videos young woman. I like that you seem to concentrate a bit more on the advanced features of VBA. 👍

[@andi.setiadi]

Excellent explanation! Clear and easy to understand. The details provided are very insightful and make the concept easily accessible for everyone. Great job

[@noviceprogrammer2011]

I believe this is an example of composition, which is an alternative to inheritance. Hope you can make some more similar videos and show if / how SOLID principles apply in VBA too.

Awsome video!! Just found your channel today. Thanks a lot!

[@jmathew6988]

Excellent tutorial, like all your previous ones. Thanks for the great tip on how to prevent the compile errors pop-up. The loud alarm accompanying the pop-up was really irritating and whenever it happened, more often than not I would end up inadvertently clicking 'help' rather than 'close'. It meant having to wait for a really useless help textl to load and having to close an extra window. It used to rattle me every time. The whole thing had developed into a sort of phobia. Not exaggerating by saying that life has turned much easier because since I got rid of that pop-up. The silent red lettering is comparatively such a gentle and polite way to be alerted. Thank you ! 😊😅 p.s.You have an incredible voice.

[@iamjojo999]

I learned alot from you, thanks, really looking forward to your next video about qualification at 56:00😊

[@armaghankhan3938]

Thanks Jennifer for creating this video

[@jamesthomas8249]

Liked the video, but what are the advantages to using the "getters & setters" over just setting the properties as Public and validate data in code that creates the class?

[@iamjojo999]

Using getter and setter is more flexible than one public statement. For example, by using setter (a subroutine), you can assign variable some value then do something else. For example,when setter set apple amount, you can write some code below it to calculate how much of these apples, then when you give value to setter in a normal module l, the class will take your value then calculate the amount. Another advantage of using getter and setter is that you can choose to or not to use either of it. If you only use setter and private statement, then user can only assign value to variable but can't retreive it. It's the same on the contrary. If you want to protect variable from changing value from outside the class,then simply write getters only. Hope this is clear.

[@jamesthomas8249]

@@iamjojo999 Thank You. Yes, I think I can apply your examples in my employee and Inventory classes. Protecting cells feature will be especially useful. Very much appreciate your quick response.

[@ravirajguru7044]

Great!, Also Please share this sheet if possible. Thanks for the videos

[@robertherzog2087]

I don't understand how the employee, person, and address get linked together in your examples. Can you please explain the specific aspect of your code?

[@carolinaoviedo1172]

Hi Robert, do You still need some help with this?

[@robertherzog2087]

@@carolinaoviedo1172 Thanks for replying. I think I figured it out, but it wasn't explained very clearly.

[@AbdulRahmanSABRA]

Very informative

[@svsin440]

❤❤❤

[@sebastian1200]

Using public enum is not the best solution. What’s more the class is not usable without that module with public declaration. The class should be usable on its own.