<!-- June 6 2008,  Chris Marek
// How this web site finds the Javascript files.......
// The NoAuth.master file has as part of its GUI.... <script type="text/javascript" src="Reports.js"></script>
// Also the NoAuth.master file has as part of its GUI <body onload='StartPage("ctl00_ContentPlaceHolder1_");'>
// As a result, any pages that inherit from the NoAuth.master will have these pieces incorporated into their pages as well. 
// (as you can see in View Source on the rendered page) Unfortunately, not all pages in this website will have the correct 
// directory structure for the <script type="text/javascript" src="Reports.js"></script> and when those pages try to execute
// the onload='StartPage() javascript, they will fail to find the Reports.js file (where StartPage() resides). If Javascript 
// debugging is turned on, it will detect the broken javascripting and pop up an error warning. To prevent this, until I can 
// think of a better way, I have placed this "stubbed" Reports.js file in this directory so that the pages in this same directory 
// will find it on their page loads. Thats all this is here for, it has no other purpose. The "real" Reports.js file is where 
// it belongs in the Reports folder with the pages that actually use it. 
// I am sure there is a less cludgey way to do this. I experimented with ClientScriptManager in Reportmain.aspx.vb, and that worked 
// fine only if the pages did not use the 'javascript:history.back()' to Navigate back to a page. When that is used, the Javscript 
// would execute too early in the page cycle, and not see the values that got placed back into the web controls by the browser 
// AFTER the Javascript ran.
 function StartPage()
 {
 }    

// -->