Run Time Errors
Trending Topics
#9
Guest
Posts: n/a
Fodor's editors here. Thank you for posting about the error that is occurring on Fodors.com. We would like to fix the problem but we need more information. Can you please e-mail us ([email protected]) and specify what page on Fodors.com this is happening on, and the exact error message you are receiving? <BR>Many thanks, <BR>Fodors.com Editors and Producers
#10
Guest
Posts: n/a
At work on a pc with windows 2000 and ie 6.0 something I get 'run time error at line 48' 'do you want to debug?' press yes and all is ok.<BR>At home on a pc with xp home and ie 6.0 something I get nothing.<BR>Also have pop up stopper at home so maybe the error is with the pop up?
#12
Guest
Posts: n/a
Yes, me too.....a small little square immediately up the first page opening of fodors.com. Whether I click the "x" in the upper right, OR click "yes" (I want to debug) or "no"...it disappears and sometimes returns and sometimes not. Then I just proceed with your page. Glad it's not just MY computer.
#20
Guest
Posts: n/a
In a fairly simple explanation, a run time error is one that happens because of a flaw or a "bug" in an otherwise functioning computer program that causes a problem to the computer system.<BR><BR>All computer applications, such as one that runs a web site on Internet, operate under the overall supervision of a computer operating system, OS. I do not know exactly which OS Fodors runs, but it looks to me like a version of Unix. <BR><BR>One of the jobs of the computer operating system is to manage several programs (also called applications or processes) that are in progress at the same time. As part of the management task, the OS protects other programs from a program that has a severe bug in it.<BR><BR>If the buggy program tries to do something that threatens to disrupt or damage another process, the OS steps in. <BR><BR>Sometimes the OS shuts down the whole buggy program. In the case described above, it seems like a certain series of control keys can get around the error and in other cases something weird happens. How and why the error acts as it does gets hairy to explain. It is also even hairier to find and fix, particularly if you cannot reproduce the problem. That is why Fodors' editors need highly specific info.<BR><BR>Just telling them that there is a problem does not give them enough specific information to replicate the problem. It is quite possible that the error does not happen all the time; it takes a precise mix of operational conditions to cause it -- a mix that cannot be easily duplicated in single user mode when the users are shut out of the system. <BR><BR>I don't see the error when I access Travel Talk on my system, so I have not experienced it first hand. I am not sure why I don't see it. Perhaps it is because I don't have the latest IE browser. All browsers are quite different under the skin and it is quite possible that there is something about version 6 that tweaks the Fodors operating system and makes it think something is wrong. <BR><BR>I also use Netscape, and I still run version 4.74 because it works, particularly with one of my email servers. So in neither case do I provoke the run time error response. <BR><BR>My practice over the years has been to leave a working system alone. Don't switch to a new model until you can't do what you need to do. If it ain't broke don't fix it.<BR><BR>Hope this helps. But believe me, understanding just how a run time error pops up is hard. I don't think it is possible to understand the depth of the problem without a working knowledge of how a given operating system works. Also, the OS is a very complex entity that requires highly technical skills to develop. If the error is in the IE browser, it will be the devil to trace.<BR><BR> <BR>

