Re: Error 1308 comparing strings

Tech-Archive recommends: Fix windows errors by optimizing your registry



"Devers" <Devers@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BC6181E8-7C2B-4B4C-AAEF-40F2175D3AD4@xxxxxxxxxxxxxxxx
> I'm getting an error 1308 (Insufficient Stack Space) when comparing a
> string
> and a memo field with lengths of 169,378 chars and 338,852 chars
> respectively. The command is simply: IF lc_Notes <> cCUST.cu_notes
>
> If I put the string into a memo field in a cursor and then compare the two
> memo fields, I get the same result. Ditto for putting the memo field into
> a
> string and comparing the two strings. The Help for system capacities
> states
> that character strings or memory variables can be 16,777,184 characters
> long.
> Has anyone else run across this problem, and what would you suggest for a
> work-around? (Besides chopping up the string into 100K pieces for
> comparison,
> that just sounds cheesy to me.)

In FPW2.6 I've compared much bigger strings when I've read complete files to
a variable with FREAD() to see if they are identical or not.

Is the command anywhere within a lot of recursion?

--
Regards
Andrew Howell


.



Relevant Pages

  • Re: Error 1308 comparing strings
    ... Works fine for me in VFP9 in the command window. ... >>> a string and a memo field with lengths of 169,378 chars and 338,852 ... >>> memo field into a string and comparing the two strings. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Error 1308 comparing strings
    ... Version of Windows? ... >>> a string and a memo field with lengths of 169,378 chars and 338,852 ... >>> memo field into a string and comparing the two strings. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Error 1308 comparing strings
    ... Do you get the same error if you extract the offending line of code out of ... > If I put the string into a memo field in a cursor and then compare ... > memo field into a string and comparing the two strings. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Performance RPG Figurative Constants versus Literals
    ... in compilation times between the two methods, ... I would suspect that the compiler would store *blanks as a single byte ... I would also suspect that comparing ... a 132 character string to a figurative constant would be quicker in the ...
    (comp.sys.ibm.as400.misc)
  • Re: A more efficient way
    ... > Is there a more efficient way of comparing a string to different words? ... the limit," 20.17's suggestion leads to hashing schemes which ...
    (comp.lang.c)