I am relocating an old Intranet site between a servers (let's call
them oldserver and newserver), and I'm having issues with viewing some
snapshots.  It seems that the ASP page in question *must* have the full
URL hard coded to the snapshot location in the SnapshotPath parameter to
work.

Here is an example of the current code:

<OBJECT ID="SnapshotViewer" WIDTH=100% HEIGHT= 300
  CLASSID="CLSID:F0E42D60-368C-11D0-AD81-00A0C90DC8D9" border="0">
<param name="_ExtentX" value="18336">
<param name="_ExtentY" value="10054">
<param name="_Version" value="65536">
<param name="SnapshotPath"
  value="http://oldserver/app/db/FirstName.snp">
<param name="Zoom" value="0">
<param name="AllowContextMenu" value="-1">
<param name="ShowNavigationButtons" value="-1">
</OBJECT>

If I update SnapshotPath to change "oldserver" to "newserver",
everything works OK on newserver.  However, when oldserver is retired I
will be using a DNS alias to point oldserver to the IP address of
newserver.  It seems that when the server name in the URL doesn't
exactly match the name in the parameter, I get an error (this also
occurs using the IP address directly):

Snapshot Viewer Control:
This page is accessing information that is not under its control.
This poses a security risk.
Do you want to continue?   Yes/No

Selecting yes works, but will be a little aggravating to our users :-)

I tried removing the server name from the parameter so that it reads:

<param name="SnapshotPath" <value="/app/db/FirstName.snp">

...but that causes it to error no matter what server name you use in the
URL.

Does anyone know if it is possible to use relative paths with the
embedded OCX?  Are there any other ways to get around this issue?

TIA,
Andy.