Group: StrataFrame Developers
Posts: 6.6K,
Visits: 6.9K
|
Glad you got it...we take an entirely different approach to MRUs within our applications. Depending upon where and what are are doing, we may use a combo. But in other cases we use a ListView on a "Getting Started" page. But this really isn't my point on th topic...we actually serialize and store the MRU information on a per user basis in the SQL database itself. This way when a user goes from one machine to the next, their MRUs are still there. Additionaly, we have a single column to query for the user and object state type. We have a MRU base class that we inherit and create for each type of MRU that may need to be created (i.e. patients, codes, templates, etc.) We then serialize the MRU collection to a VarBinary field in an ObjectStates table. So when a user gets to a certain combo/list/whatever, the MRU specifically for them is retrieved and the populates the object in question from the serialized object model. These are just some ideas I thought I would throw out there since you brought up an MRU...this has been a huge hit...especially since it is by user and not specific to a machine.
|