Re: [StrongED] "string not recognized" error

[Jim Nagel <stred@xxxxxxxxxxxxxxxx>]

Fred Graute  wrote on 30 Aug:
...
> error doesn't always occur. My suspicion is that one of the system
> variables used in ClaimFiles is being corrupted somehow. I did manage to
> reproduce this when Jim first mentioned the problem but I can't remember
> how I did it. Basically the value assigned to the system variable isn't
> a legal string, eg a doublequote too few or too many.


> Jim - To try and catch the error, copy ClaimFiles to StrED_cfg.UserPrefs
> and add the following line just under the first three comment lines:

>   X ReportCmdOn

> This will cause all commands executed from ClaimFiles to be sent to
> Reporter. The X is there to catch errors when Reporter isn't running.

> At the end of the file add this:

>   X ReportCmdOff


> When the error occurs it should be logged by reporter along with the
> command that triggered it. That should help identify which variable is
> giving trouble. Getting the values of the relevant system variables is
> also helpful, so when the error has occured run the following obey file
> in a TaskWindow:

>>----- Start obey file

>   Show Alias$@RunType_FFF
>   Show Alias$@EditType_FFF
>   Show OLEServer$Type_FFF
>   Show OLEServer$Type_FFB
>   Show TaskWindow$Server
>   Show Alias$TaskWindow

> <----- end obey file


> Post the log from reporter and the output of the obey file here so that
> we can see what's happening and work out a solution.


OK, the error is occurring again after booting up today, after several 
days of using StrongEd without problem.

here is the result of the obeyfile Fred prescribed:

Alias$@RunType_FFF : Run ADFS::IDEDisc4.$.Apps-J2.!StrongED.!Run %*0
Alias$@EditType_FFF : Run ADFS::IDEDisc4.$.Apps-J2.!StrongED.!Run %*0
OLEServer$Type_FFF : -N OLESupport -R Desktop_OLESupport|@
TaskWindow$Server : Resources:$.Apps.!Edit
     
i notice that only four of the six lines in the obeyfile produced an 
answer -- ie, lines 4 and 6 got no response.

here are the relevant lines from the Reporter log:

     Reporter 2.64d (23 May 2006)   List  Mon 6th Sep 2010  17:07  
     
     16:58:31.97 ** ReportCmdOn  **
     | 100830 added above line at Fred Graute's suggestion to try 
     to trap "string not recognized" error
     |
     
     Unset Alias$@RunType_FFF
     |Unset Alias$@EditType_FFF
     |Unset OLEServer$Type_FFF
     |Unset OLEServer$Type_FFB
     |Unset TaskWindow$Server
     |Unset Alias$TaskWindow
     
     | Claim file type and external edits.
     If "<Alias$@RunType_FFF>" = "" Then Set Alias$@RunType_FFF 
     Run <StrongED$Dir>.!Run %*0
      Set Alias$@RunType_FFF Run <StrongED$Dir>.!Run %*0
     Keyset Alias$@RunType_FFF Run <StrongED$Dir>.!Run %*0
     If "<Alias$@EditType_FFF>" = "" Then Set Alias$@EditType_FFF 
     Run <StrongED$Dir>.!Run %*0
      Set Alias$@EditType_FFF Run <StrongED$Dir>.!Run %*0
     Keyset Alias$@EditType_FFF Run <StrongED$Dir>.!Run %*0
     
     | Claim linked and embedded objects.
     If "<OLEServer$Type_FFF>" = "" Then Set OLEServer$Type_FFF 
     -N StrongED -R /<StrongED$Dir>
     String not recognised
     Exec
     Exec
     

any clues gratefully received!  thanks.  --jim


-- 
Jim Nagel                        www.archivemag.co.uk

-- 
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx