Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Macro substitution error (maximum statement length?)
Message
De
08/10/1999 07:44:44
Wim Dieke
Tranquility Bv
Almere, Pays-Bas
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00272599
Message ID:
00274123
Vues:
46
>>>Wim,
>>>
>>>Then change it to;
>>>
>>>MessageBox(EVALUATE(Table.ErrorCommand))
>>
>>Nope, this one will not do becourse the evaluate(cExpression) does not allow cExpressions > 255 chars.
>>
>>But thanks anyway.
>
>Wim,
>
>Then your only choice is to break up the macro;
>
>

>LOCAL lcMacro1, lcMacro2, lcMacro3
>
>lcMacro1 = SUBSTR(FieldName,1,200)
>lcMacro2 = SUBSTR(FieldName,201,200) && check these numbers (not tested)
>lcMacro3 = SUBSTR(FieldName,401,200)
>
>MessageBox( &lcMacro1 &lcMacro2 &lcMacro3)


That is correct Jim. I came to the same conclusion today. For your (or others that read this) info: the above code will not work, becourse it could break up commands and/or functions. I have choosen to break up at the CHR(13) positions automaticly. I have given the restriction on the table that the length of the items between two chr(13)'s must be less than 250. It seems to work ok now.

Anyway, thank you all for your help and effort.
---
Life is like a box of chocolates
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform