Errors Output
  1. no include header.inc at /usr/lib/perl5/vendor_perl/5.10.0/Apache/ASP.pm line 1216. , /usr/lib/perl5/vendor_perl/5.10.0/Apache/ASP.pm line 1522
Debug Output
  1. no include header.inc at /usr/lib/perl5/vendor_perl/5.10.0/Apache/ASP.pm line 1216. , /usr/lib/perl5/vendor_perl/5.10.0/Apache/ASP.pm line 1522
ASP to Perl Script 

  -: use strict;;;use vars qw($Application $Session $Response $Server $Request);;
  -: #line 1 /sites/spencer/htdocs/about/why.asp
  1: ;;&Apache::ASP::WriteRef($main::Response, \('<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
  2:         "http://www.w3.org/TR/html4/loose.dtd">
  3: <html>
  4: <head>
  5: 	<title>www.spencer.com</title> 
  6: 	<meta name="generator" content="BBEdit 7.1.4">
  7: 	<link rel="stylesheet" type="text/css" href="/styles/layout.css">
  8: 	<link rel="stylesheet" type="text/css" href="/styles/content.css">
  9: </head>
 10: <body>
 11: 
 12: ')); &sapl::header({  'location'=>""  }, ''); ; &Apache::ASP::WriteRef($main::Response, \('
 13: 
 14: <div class="fullContent">
 15: 	<P class="heading">
 16: 	Why Spencer &amp; Associates
 17: 	</P>
 18: 		<p class="body">
 19: 			Since 1989, Spencer &amp; Associates has been dedicated to the pragmatic, timely, and
 20: 			cost-effective resolution of key business issues, regardless of project size. By addressing
 21: 			causes, not just symptoms, we contribute knowledge as well as value. Our approach is founded on
 22: 			exceeding expectations and a commitment to the success of our clients. Our methodologies
 23: 			include:
 24: 		</p>
 25: 		<ul>
 26: 			<li>
 27: 			Focused project goals</li>
 28: 			<li>
 29: 			Clearly defined project responsiblility</li>
 30: 			<li>
 31: 			Frequent client communication</li>
 32: 			<li>
 33: 			Thorough analysis and clear presentation of results</li>
 34: 			<li>
 35: 			An uncompromising commitment to integrity</li>
 36: 		</ul>
 37: 
 38: 	<div class="bodyBlock">
 39: 		')); &sapl::bulletHeader({  'color'=>"saplred" }, 'Experienced'); ; &Apache::ASP::WriteRef($main::Response, \('
 40: 		<p>
 41: 			Our hands-on operating and executive experience produces viable solutions that
 42: 			acknowledge each client&rsquo;s cultural and business realities
 43: 		</p>
 44: 		')); &sapl::bulletHeader({  'color'=>"#FF9900" }, 'Effective'); 
 45: ; &Apache::ASP::WriteRef($main::Response, \('
 46: 		<p>
 47: 			Communicating effectively at all organizational levels&mdash;executive through
 48: 			marketing, engineering, and product line management&mdash;we can rapidly achieve product
 49: 			objectives
 50: 		</p>
 51: 		')); &sapl::bulletHeader({  'color'=>"saplyellow" }, 'Responsive'); ; &Apache::ASP::WriteRef($main::Response, \('
 52: 		<p>
 53: 			One of our significant advantages as a small company, we provide personalized
 54: 			service by working one-on-one with each client with direct executive involvement;
 55: 			our staff is readily accessible by telephone and e-mail to respond to any questions
 56: 			or concerns, promptly and effectively
 57: 		</p>
 58: 		')); &sapl::bulletHeader({  'color'=>"#99FF00" }, 'Independent'); 
 59: ; &Apache::ASP::WriteRef($main::Response, \('
 60: 		<p>
 61: 			We understand the business objectives of independent testing, and work with our
 62: 			clients to position the results to their best advantage without compromising
 63: 			integrity; we are simultaneously proactive and team players
 64: 		</p>
 65: 		')); &sapl::bulletHeader({  'color'=>"saplgreen" }, 'Innovative'); ; &Apache::ASP::WriteRef($main::Response, \('
 66: 		<p>
 67: 			Recognizing the need for controlled and unbiased testing, we have developed
 68: 			industry-standard printer test software suites that facilitate Print Quality
 69: 			evaluation&mdash;by providing idealized source data, we can expore the limits
 70: 			of the printing device under test; and by designing metrics directly into the test
 71: 			patterns, we can acquire many objective results without sophisticated
 72: 			instrumentation, while establishing the data for more sophisticated analysis when it
 73: 			is available
 74: 		</p>
 75: 		')); &sapl::bulletHeader({  'color'=>"#00FFFF" }, 'Industry-Relevant'); 
 76: ; &Apache::ASP::WriteRef($main::Response, \('
 77: 		<p>
 78: 			Advising the color-peripheral industry and performing independent product analysis,
 79: 			we have the extensive base of industry contacts and resources required for timely
 80: 			resolution of complex business and technological issues
 81: 		</p>
 82: 		')); &sapl::bulletHeader({  'color'=>"saplblue" }, 'Cost-Effective'); ; &Apache::ASP::WriteRef($main::Response, \('
 83: 		<p>
 84: 			We understand the need to work within realistic client budgets&mdash;rather than trying
 85: 			to be the lowest bidder, we strive to provide the <i>highest value</i>&mdash;our relevant
 86: 			expertise and project orientation produce quality, cost-effective results
 87: 		</p>
 88: 		')); &sapl::bulletHeader({  'color'=>"#FF00FF" }, 'Confidential'); 
 89: ; &Apache::ASP::WriteRef($main::Response, \('
 90: 		<p>
 91: 			We provide services to multiple clients that may be deemed direct competitors&mdash;these
 92: 			services are provided on a confidential basis, and the results are not available to
 93: 			other clients or any other entity unless released by the contracting client; by maintaining the integrity of our work and the
 94: 			confidentiality of our clients, we have built a reputation of trust
 95: 		</p>
 96: 
 97: 	</div>
 98: 		<p class="body"><br>
 99: 		<span class="emphasis">Spencer & Associates Publishing, Ltd.</span><br>
100: 		Three Giffard Way, Suite A<br>
101: 		Melville, NY  11747-2310 USA<br>
102: 		1-631 367-6655, fax:1-631 367-2878<br>
103: 		info@spencer.com
104: 		</p>
105: </div>
106: 
107: ')); &sapl::footer({   }, ''); ; &Apache::ASP::WriteRef($main::Response, \('
108: 
109: </body>
110: </html>'));


An error has occured with the Apache::ASP script just run. If you are the developer working on this script, and cannot work through this problem, please try researching it at the Apache::ASP web site, specifically the FAQ section. Failing that, check out your support options, and if necessary include this debug output with any query.