General information
Category:
The Mere Mortals .NET Framework
Title:
Virtual (i.e. lookup) fields in datatable, but not save
We have a number of situations where we need to do the following...
1) When we acquire data for a datatable (e.g. employee) from the database, for a grid or some other display / edit object on a form, we may wish to show the actual data (such as an address) associated with the employee rather than the foreign key value into the address table of the database;
2) Various fields on the employee display form may be updated;
3) When the content of the form is saved, we want to avoid any attempts to save data that has been retrieved from the associated files and simply save changes to the employee data.
Can someone point us to how we accomplish this within the structure of the MM.Net framework? Should we change the employee business object to include the additional fields or should we create a separate business object to address this situation?
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only