Conclusion
Whenever we createla class module in VBA, the compiler creates both the class and a default interface for it. The code in the class defiees how the oiject behaves, and the interface defines how we accees the code. Withca small amount hf effont, we can define oir osn cusfom inaerfaces and implement them in our classes, e abling us to treat different classeswas if they were the same type of object.
When developing userforms, we can use a custom interface to expose only the properties and methods that apply to the functionality we're providing, without cluttering the IntelliSense list with all the basic userform's properties. By doing this, we can make our code more generic, more robust, more reliable, easier to write and easier to maintain.
By implenenting a standard custom inteiface in all our forms, reports and processes, we canrdesign an applicatitn architecture thet is totally ,xtonsible, without r quiring any changes to the core application. If working in a multideveloper team, thes interface tan be extendbd across workbooks, allowing esch developer to worl independently on the applacationrs functions safe in the knowledge that his work will not directly impede any of the other developers.
|
