decoupled generic key-value access against linq in a non-xml environment

good morning.

i am not a computer scientist by education, so please overlook any shady term abuse.

in my framework, a base form called Record opens form RecordDetail as dialog. for example, RecordClient extends Record and contains client data and tabbed lists of client-relevant child data, and RecordDetail expands one child data row for detailed editing based wholly on reflection and display overrides stored as custom attributes used against DataContext. Record is subclassed for the application, but i see no need to subclass RecordDetail. this works except for the display of foreign key edits in the listed children.

i must use ObjectListView and Linq; i cannot use WPF/XML. because i do the serialization trick for non-continuous database connectivity, i lose foreign key objects when i clone data to manage state. ObjectListView needs the foreign key object for display and general wickedness. i know Hibernate, but Linq leaves me at a loss:

how might i access the foreign key object from within Record after its dialog to RecordDetail closes - without coupling framework and application-specific classes?

that is,

Type rowType = row.GetType();
IDomain workDamnit = (IDomain)dataContextReflectedFromRowType.GetTable(rowType).Where(x => x.PrimaryKey == 1).SingleOrDefault();

where "PrimaryKey" wraps the primary key at开发者_运维技巧tribute, and the fail happens between "GetTable", "Where" and "SingleOrDefault".

any perspective appreciated on this fine sunday morning.

actually, i've decided to uncle under and cache the foreign key objects in a pool accessed by the subclassed Record forms.