Re: Breaking Long Query into multiple statements ?

Hi Tony,

Did you use those in the scan as example.
Scan for &var1 &var2 &var3
Yes. In old versions of foxpro there was a limit with the length for each single variable involved in macro expansion. This limit was about 256 characters. But composing a line by more than on variable was possible up to the command line length limit of 2K.

What version of foxpro do you use?

> I tried joining them like
> var4 = var1+var2+var3
> and then
> scan for &var4
> Did not work.


Attention, there is a little difference between
Scan for &var1 &var2 &var3
and
Scan for &var1&var2&var3
In the first line there are some more blanks in the resulting command.
Maybe these blanks are needed or the are not allowed or they don't matter. It depends on your varN.

Regards
Bernhard Sander
.

Relevant Pages

  • RE: inserting the max colum in the stored proc
    ... Create Stored Procedure Name ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: inserting the max colum in the stored proc
    ... Create Stored Procedure Name ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Misnomers in the COBOL standard
    ... I always liked it that COBOL nearly always worked left to right: MOVE VAR1 ... TO VAR2, ADD 1 to VAR3, etc. ... DIVIDE A BY B would have broken this which is why it requires GIVING. ...
    (comp.lang.cobol)
  • Re: Misnomers in the COBOL standard
    ... William Bub wrote: ... I always liked it that COBOL nearly always worked left to right: MOVE VAR1 TO VAR2, ADD 1 to VAR3, etc. ...
    (comp.lang.cobol)
  • Re: [PHP] string as file
    ... This is an example of $var1 and $var2. ... I think that neither you nor Greg understands what I'm looking for. ... Use regular expressions or straight string replacements - that's the best way to implement mail-merge type behaviour. ...
    (php.general)