View Complete Thread | FoxWeb Forum Home
Search:
Date:    Msg ID:   
From:    Thread:   
Subject:   
The Run as Service has always been unchecked.
I Unchecked Hide windows.
I edited the code to put back the error condition, which is a line like:
IF NOT EMPTY(FILETOSTR(lcPssErrorFileFullPath))
where the file referenced in lcPssErrorFileFullPath was never created.  The develper box running 1.29 showed this error on the web page and the line it occured at, but the 2.11 version just timed out.
 
So after I changed the above code back to the bug I ran the Web App.
I looked at the FoxWeb channels and FoxWeb1 Channel showed busy.
I looked at the window and it showed some text about the server and no pop-up windos showed up at all.
I waited and the Web App timed out like was reported and the FoxWeb1 channel went from busy to waiting.
 
I am running the FoxWeb 2.11 version on a Win 2000 Server box.  FoxWeb has a 2 server license running also.
 
Any thing else you need just ask.
 
Bret
Sent by FoxWeb Support on 01/17/2003 12:52:51 AM:
The timeout probably occurs because something in your code causes the FoxWeb channel to pop up a dialog, asking for user input.  To verify this, disable the Run as Service and Hide Channels options and restart FoxWeb.  Open the channel windows and arrange them on your screen, so that you can see them all at the same time.  Now call your script and see if a window pops up.
 
I don't know why the two versions would behave differently, but if this is a different server, it is possible that FoxWeb can simply not find a particular table on your 2.11 server.

FoxWeb Support Team
support@foxweb.com email

Sent by Bret Hobbs on 01/16/2003 10:39:23 AM:
We have installed the new FoxWeb version 2.11 using our existing 1.29 Code (option set).  We will be converting our 1.29 code over as time permits.  But the new server using FoxWeb 2.11 has been  timing out on us today.  When I went back to our developer server (which still uses 1.29) and ran the code.  It reported a bug in a section of my code, that was never reached during our initial testing.  I then edited the code and it fixed the bug on the developer machine.  The 2.11 machine never reported the error it just reported a time-out error (because it past the Time-Out setting).  So if I never had the developer server with 1.29 still on it I would not have found the error without some major debugging time.
 
My question is when running old 1.29 code on the 2.11 version is there a setting that will get FoxWeb to report errors back as 1.29 did and not just time out?
 
Thanks
 

The early bird may get the worm, but the second mouse gets the
cheese.