Look into the step-by-step process creating  a data  Form Web Part. You
can create this Web Part using SPD and selecting Data View/Insert Data
View and/or Manage Data Sources. Make sure you create the data source
connection to the Source from which you want to create the view  which is
the destination to the InfoPath Form.

The way to do this would be to promote the fields that you want to use for the
new view  when you publish the form  to the library. That way those fields will
be available when you are in the modify or create a view page.

Did you see my question related to modifying the alert URL for external
users who receive alerts? The URL points to an internal URL. Whereas,
it should point to the external URL. I have copied the
AlertTemplates.xml file and now need to modify the return URL. However,
I am not sure where to modify this in the BNIAlertTemplates.xml (copy
from AlertTemplates.xml). Here is the new XML file that I need to
modify to point to the external URL where I will then run STSADM -o
updatealerttemplates -url <http://urlname> -filename <your working copy
filename>.

What I am thinking is that the SiteURL variable name is pointing to the
internal URL. If this is true, how do I modify the variable name to
point to the internal URL?

Alerts will use the Alternate Access Mapping address that the user who creates
them uses. If the alerts are created by a user inside the network for someone
else then they will reflect the internal address. If they are created by the
external user then they should default to the external address. I suspect there
are two possibilities for why you are getting the wrong address.

1. The alerts were created by an admin for the external users while the
admin was logged in on the internal address. The easiest way to do this is to
delete and re-create the alerts while logged in through the external address.

2. Your external address isn't actually an AAM, but something being
handled by a proxy server or ISA server. I don't know enough about your design,
but this could be an issue.

#2 is possible but a long shot. #1 is more likely. I would not try to hard
code the AlertTemplates.xml file to fix this. You should make sure the alerts
were created the right way and re-create them if necessary. As I remember there
is also an STSADM command that will do a bulk change of the alert address, but I
don't think this will work in your environment if you have regular internal
alerts that need to stay internal.

Well, I believe the alternate access mappings was the problem. I moved
the external URL to Default Zone and moved the internal URL to Intranet.
I believe that should solve the problem. I had the external URL in the
Extranet Zone, the internal URL in the Default Zone.