Date:  12/15/2008 01:36:47 PM Msg ID:  003881
From:  FoxWeb Support Thread:  003876
Subject:  Re: Strange Errors in v4
If the reported code does not match the actual script, this is usually an indication that the script source does not match the fxp file. Please  check the FoxWeb Program Root folder:
  1. Is there a file named checkinpost.fwx? What's the modification timestamp?
  2. Is there a file named checkinpost.prg? What's the modification timestamp?
  3. Is there a file named checkinpost.fxp? What's the modification timestamp?
Compare the timestamps. The fxp timestamp should be newer than the timestamp of the scripts themselves. You may want to delete the .fxp file and let FoxWeb re-create it.
 
While you are at it, please zip the above files and send them to us via email.
FoxWeb Support Team
support@foxweb.com email
Sent by Curtis Hertwig on 12/15/2008 01:18:59 PM:
As I said, line 57 of checkinpost2.fwx is a blank line.

I have recompiled all scripts since upgrading.
<font color=red>     -cjh</font>
Sent by FoxWeb Support on 12/15/2008 01:14:22 PM:
According to the error log you mailed to us, the error is occurring in line 57 of a script named checkinpost2. I would look at the code from that script for the source of the error.
By the way, did you happen to upgrade to a newer version of FoxWeb, or changed from using the VFP run-time DLL to using the full version of VFP, or vice-versa? If yes, you should re-compile all your scripts, using the Compile tab of fwadmin.fwx.
FoxWeb Support Team
support@foxweb.com email
Sent by Curtis Hertwig on 12/15/2008 01:02:20 PM:
 There is no custom error handler in place. Error file has just been emailed.
<font color=red>     -cjh</font>
Sent by FoxWeb Support on 12/15/2008 12:41:20 PM:
The line below does not exist in the FoxWeb code either. What do you mean by "random times"? Do you get this error when you call FoxWeb scripts, or do you see it in the FoxWeb error log? Regardless, if it is generated by a FoxWeb script, you should be able to find a corresponding entry in the error log. Please export the error entry via fwadmin.fwx and email it to us.
Another possibility is that you are using a custom error handler with this code. Look in that error handler for the offending line.
FoxWeb Support Team
support@foxweb.com email
Sent by Curtis Hertwig on 12/15/2008 12:24:14 PM:
 I recently upgraded from v3 to v4 of FoxWeb. Since that time, at seemingly random times I get error #45 (Not a Character Expression). The error report cites a blank line and shows the line as either:
   lnrows = ASTACKINFO(laStack)
or
   eventstrigger()
Neither of these lines exists in my code.

<font color=red>     -cjh</font>