I am developing this in Access, but want to make sure that if I do migrate this over to .NET it is a smooth transition. I want to follow good OO implementation and methodology. I want to ensure that this is scalable and any addition of other modules is a smooth easy transition. I want to make...
Data Access Object
I apologize if I wasn't clear. I do currently store collections of object within an object. The problem is that I want to keep the DB connectivity in a separate class from the Object itself. From a development perspective this makes cleaner code and will be easier to...
I am posting this here because this is where I felt I would find the brilliant minds who are familiar with OO theory rather than at the MSAccess Forums. So bear with me.
Background:
I am trying to write a VBA app using OO methodology. This allows for the DB adn the Code to live...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.