I can reproduce the problem more or less reliably, but i can not discern any patterns. I took a look at the source. The source in the web-browser looks like this:

17.09.04

Fr

'+lcdatum+'

'+chr(13)) response.write('

'+zkt.anz_wt+'

'+chr(13)) response.write('

'+zkt.anz_stemp1+'

'+chr(13)) response.write('

'+zkt.anz_funk1+'

'+chr(13)) response.write('

'+zkt.anz_stemp2+'

'+chr(13)) response.write('

'+zkt.anz_funk2+'

'+chr(13)) response.write('

'+zkt.anz_sollz+'

'+chr(13)) response.write('

'+zkt.anz_istz+'

'+chr(13)) response.write('

'+zkt.anz_abw+'

'+chr(13)) response.write(''+zkt.anz_zkt+''+chr(13)) In my opinion it could not be a problem of data access collisions in two frames. Everthing is handled from the main fraim, in wich the problem occurs. Should i install any updates of XP (Professional) or Foxweb or how can i solve this problem? Sent by FoxWeb Support on 10/18/2004 12:38:51 PM: Is it possible for you to reproduce the problem reliably, or is it completely intermittent? Intermittent problems are always harder to troubleshoot, because it's difficult to discern patterns and know when to start a debugging session. One thing I would suggest is to View Source in the frame that fails to be displayed completely. The way to do this is to right-click in the frame area and select the View Source option from the pop-up menu. Selecting View Source from the main menu is not the same when you are using frames, because it shows the source of the top-level frameset document instead. Could it be that two frames in your application are causing data access collisions? One thing you need to always consider when writing applications that run in frames, is that the various frames may be calling fwx scripts simultaneously. It is your responsibility to make sure that this will not cause problems. FoxWeb Support Team support@foxweb.com email Sent by Timo Biedenbender on 10/18/2004 07:11:46 AM: Hallo, after your answer, I changed script timeout to 60 seconds, but nothing has changed. The FoxWeb Error Log and fwstart.log do not have any entries at this time. What kind of procedure for debugging should be the best. I will try it. Sent by FoxWeb Support on 10/16/2004 02:25:47 PM: It's possible that this is a timeout problem, but it's impossible to know without getting more information from you. Have you use the procedures listed under the Debugging FoxWeb Scripts section of the FoxWeb documentation? At the very least you should look at the FoxWeb Error Log and the file fwstart.log. The latter will tell you if any channels have timed out and were restarted. FoxWeb Support Team support@foxweb.com email Sent by Timo Biedenbender on 10/15/2004 12:32:50 AM: Hallo, we are using Foxweb (Version 2.11) and have sometimes a problem with one website. We are using IIS 5.1 with Windows XP Professional SP 1. This website is a frame of a frameset. When it is called, it shows data of the current month. The user can select anoter month and the website is calling itself and displaying data of the selected month. Sometimes, the website is not displayed completely. The table stops somewhere. In this situation, you can not see the complete code in the webbrowser. Sometimes, a part of the code, wich is not interpeted, appears at the top of the table. In my opinion, it could be a problem with foxweb. Hope, someone can help us. Thanks, Timo Biedenbender