Re: [StrongED] "string not recognized" error

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <64ee004f51.old_coaster@old_coaster.yahoo.co.uk>
          Tony Moore <old_coaster@xxxxxxxxxxx> wrote:

> On 29 Aug 2010, Jim Nagel <stred@xxxxxxxxxxxxxxxx> wrote:
>
> [snip]
>
> > i don't know where these "Claimfiles" would be
>
> !StrongED.Defaults.ClaimFiles
>
> It looks as though the file is corrupt. Try replacing it with a new
> copy, from the distribution archive?

That's certainly worth a try but I don't it's problem given that the
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.

Cheers,

Fred.

-- 
StrongED developer
http://www.stronged.iconbar.com/

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