Two design implementation questions:
1. How can I configure my classes to use properties (private member variables) and accessors (getters/settors) within MM.NET? Additionally, how would I have to configure my methods to work with this design structure?
2. What is the best practice class design for a business object wherein the related database table has foreign keys that are used as lookups (code to description in another table)? Do you only include the code field in the object design or do you include the corresponding description from the primary table?
Does anyone want to share some examples of these class/business object design questions (preferable specific to MM.NET framework implementations)?
THANKS
Joe Salvatore, Programmer/Analyst - The Stellar Group