The Business Data Catalog user interface (in BDC web parts and List View web parts) does not play well with Alternate Access Mappings (AAM) in MOSS.

When you add a BDC column to a custom list, you can check the option to link the BDC value to the profile page.

When you display the items in the list in a List View or in a BDC web part, the BDC value will be a hyperlink that takes you to the "profile page" for that BDC value.

You can also drop down the context menu to the left of the BDC value to display the profile page.

This is an example of the profile page that displays:

Now, if you note in the above example of the profile page, the URL shows "devmoss2007", which is the actual hostname of my development SharePoint server.  I can view the profile page by either clicking on the BDC value or dropping down the BDC context menu and choosing View Profile.

Now let's try the same thing using Alternate Access Mapping (AAM), where we associate a different name with the MOSS server.  In this case, I am going to map the name "devmoss" to "devmoss2007".  This is done in Central Administration -> Operations -> Global Configuraiton - Alternate access mappings.

Now I will go to the same list, but use the AAM name in the URL instead of the actual hostname of the server.

Now when I click on the BDC value represented as a hyperlink:

Instead of presenting the "profile" page, it goes to this URL and does nothing:

It appears that the BDC value hyperlink is supposed to go to the _layouts/ProfileRedirect.aspx page, which then redirects to the "View Profile" page.  Except it does not do the redirect when the AAM is used to access the MOSS site containing the list or BDC web part. 

Dropping down the context menu to the left of the BDC value and choosing View Profile does work with AAM however.  So the problem is not with the BDC View Profile page, it is with the ProfileRedirect.aspx page.