> This breaks  the dataview  web part, as I had expected  it would, as I've
> been told that to have a dataview web  part to reference  a top-level
> site
> list, you need to create  it in a subsite  to begin with.

I think the issue is that while I'm using this masterpage  on the
subsite, I now realize I've made the masterpage as part  of the top-level
site.

So, I went and opened the subsite and made a new masterpage there. I go
to add a dataform and select CONNECT TO ANOTHER LIBRARY, browse to the
top level  site, and then I add the dataform web part to my masterpage.

I then try and cut-and-paste said dataform web part into my top-level's
site's masterpage, but then I'm back to square one with the 'can no load
webpart' error.

Is there a tried-and-true method to get a dataform web part in a
masterpage...regardless of what particular level site  in the portal it's
on, to always point at the exact same list on the top-level  site?

> I then try and cut-and-paste said dataform web  part into my
top-level's
> site's masterpage, but then I'm back to square one with the 'can no
> load
> webpart' error.
>
> Is there a tried-and-true method to get a dataform web part  in a
> masterpage...regardless of what particular level  site in the portal
> it's
> on, to always point at the exact same list on the top-level  site?


Well, I must have done something wrong the first time, because I got it
working.

My process:

Create a subsite.
Open it in SP Designer.
Create a new master page  within this site.
Create the dataform/view control.
Cut and paste the source code of the control and paste into the
'sub-site' masterpage  that is part of the top-level site.
Assign the subsite  to this masterpage.

That seems to work.

But is obviously tedious.

Looking at the source code, I don't see any 'aha!'
variable/setting/parameter that makes this process work. Is there
something going on behind the scenes that requires this method of
implementation?