Still learning what I am doing but http://www.btlprod.com and my Traveller Campaign link from that page both use VMP.

You would improve the end users viewing experience and have much better compatibility with browsers and OS configurations if you update your MTS3Interface and make a few changes to your HTML. You can get the latest (5.0.2.13) MTS3 at http://developer.viewpoint.com/ but a new one is due any day now.

On line 6 you have: <script language="JavaScript" src="Scripts/MTS3Interface.js"></script>
7. <script language="VBScript" src="Scripts/mtsAxDetect.vbs"></script>
8. <script language="JavaScript">
9. var vmp; // Declaration of the Object
10.</script>
11.<script language="JavaScript" src="Scripts/MTS3Interface.js"></script>12.<script language="VBScript" src="Scripts/mtsAxDetect.vbs"></script>

After you replace your MTS3 with a new one you should remove all references to the mtsAxDetect.vbs and you only need one declaration of the MTS3 so lines 11 and 12 can be removed.

This is due to using either the Dreamweaver extension or Enliven for output. (Not sure which, but I am willing to bet on the Dreamweaver-VMP extension.) Thanks for pointing it out to me.

BTW I am guessing that I also lose the line 6 </script> as well.

No you need line 6; you need at least one call to the MTS3Interface.js located where ever you place it on your server. Ideally you place it in one location on the server and then all your VET content will refer to that one location just like you now have a Scripts folder. The Output of Enliven should be correct albeit with an outdated MTS3Interface so when you get the new MTS3Interface just update the templates in Enliven and you’ll be all set for future projects.

Never mind I see where the other open Script is now.