Actually, it's not so much a matter of the view remembering where the table's dbc is - the view doesn't
care where it's table's dbc is, as long as it's open.
In my use of SDT under this data configuration, I've found that simply opening the table's database before modifying the view database with SDT works well.
Glad I could help.
Insanity: Doing the same thing over and over and expecting different results.