Frank,
I don't know the answer to your question, but I can add that the
amount of space available to your expression changes dependent
on the context in which it's used.... so from R> has the most
space, within a while loop (I think) is somewhat less...
If I remember correctly, I once shortened a lengthy expression
three times during the course of perfecting the expression from the
R>, then inside the cmd file, and then finally within the app file. I
now habitually keep things short and build expressions in small
steps. It actually seems better anyway as it's easier to understand
the expression if your looking at it in bite sized pieces.
Something like:
Set v vExp = ('Start here and add'&.v1......)
Set v vExp = (.vExp&'another step'&.v2....)
Set v vExp = (.vExp&'trying to finish'&.v3...)
and so on. I try to keep each step to something like 100 characters.
On 13 Jul 2001, at 18:37, Frank Radice wrote:
> I wrote a SET VAR v1 = ( ... expression... ) and got error message 2180
> "Expression size limit exceeded".
>
> I had about 200 characters in the expression. When I shortened to
> expression to about 175 characters, it worked OK.
>
> Does anyone know what is the expression limit? Is it based on the number of
> characters or is it based on the number of items such as variables and/or
> operators?
>
>
> Frank Radice
>
> [EMAIL PROTECTED]
>
>
