Object Orientation in Access / VBA - Should we use it?

preview_player
Показать описание
Should we use OO-Concepts in Access-VBA?
How much object orientation is supported by VBA? Does using OO make our code more maintainable?
These are the questions I try to answer with this video. It is not a how to video, but rather answers the question if we should use object oriented concepts in Access and VBA to make our applications more maintainable.
Рекомендации по теме
Комментарии
Автор

Great work Philip! appreciate your hard work...

TKondeth
Автор

Exactly right about not overdoing it.
Quickly stated, if it's possible to fix it so the compiler can catch a problem then do that rather than risk a run time error or a failed action.
I disagree on your advice on small projects though. "It's not what they want, it's what they want next" is the old programmers advice. Small projects that are done in a day or two have a way of growing into larger projects.

wilsonfineart
Автор

Thanks for a very interesting video, looking forward to the follow up.

davegoodo
Автор

Your videos are superb, but I'm not agree here. After years in VBA I have totally different conclusion- VBA is pure OO language. It is true that there is a lack of inheritance, but more important are interfaces- and it concept IS implemented and allow you tu write in a clean way. I don't know Access apps, but in Excel VBA + Userforms events (with ours Raise / With events) are essential to adopt good SOLID code with loose coupling. Cheers!

rafab.
Автор

Thanks for the elaborate explanation. At 10:35min couldn't we use the Isloaded to check if the form is loaded or open the other form in design mode to create or change controls? Can you advise if I want to create a room layout with furniture entities, would it better to use OO program like C or Java and then get the data from MS Access. I am only quite experience with VBA only.

shananarocks
Автор

What about the implements key word. Is this not inheritance?

RungeCarl
Автор

Hi, I have a question. I believe it would be easier to understand VBA and all objects hierarchy etc if you understand OO concept. OO is like the prerequisite to understand VBA. Having said that, I want an example from real life, to say that you need to learn the prerequisite first before understand this topic or that? Can you give me an example from real life, so if I want to explain that to someone, the example would help. Thank you very much.

userme