Scott, thank you again.  I think I got to where I wanted to be by simply
creating a new view.  I just repeated the top section of the original form on
the view.  Works like a charm!

Scott,

I've just started to look for a resolution to a very similar problem.  
Considering this post is about 2 years old I might find an answer as I
continue to search through the postings but wanted to respond.

First a little background...

I have a master file, master.xsn, published to a sharepoint 2.0 form library
that is being filled out as a request form.  The request form is submited via
a button in the form to another form library called 'secured' where it is
stored for access by those who complete the various requests.  This creates a
completed copy of the origional master.xsn file as xxxxxx.xml where the file
name is unique.

I did a little trick here where I took the origonal master.xsn template and
added a few additional buttons at the end to access subforms that I'm
creating as response files for the various tasks and then published the
modified template to the 'secured' form library.  Thus when the master.xsn
form is completed and submited to the 'secured' form library, the additional
buttons are added in automatically.

So far so good...this works like a charm.  The file gets published as an
.xml file with with a unique name and the addional buttons used to access the
subforms and the buttons open the subforms properly.

Here's where the problem starts....

The .xml 'copy' of the master form is then opened, and a user clicks one of
the buttons to open one of the subforms.  I've tried using data connections
to populate the fields of the subform from the form library containing the
xml documents but nothing happens.  The subform does open but I get no errors
and the fields come up blank.

I can't seem to pass the data to the new subform from the xml document that
is currently open.  Remember, each .xml file has a unique name.

I also tried using multiple views but found it didn't meet my needs.  As
each subform is completed, the subform is emailed to the origonator of the
master form.  Multiple views will create unnecessary and confusing
duplication that I'd rather not get involved with.

Any suggestions???

Thanks in advance!

Michael