Hi Sergry,

You could be right, thanks for your help. I would run a test with 40000 characters in both ways and let you know.

Doron

>>Hi Sergey,
>>
>>One more thing Macro is OK but if can take all small SQLs into 1 prg
>>then I don't need to use any Macro. The question is if I save any
>>time by breaking it to small SQLs and combing it, versus this Macro
>>substitution.
>
>I would recomend that you go with macro substitution in this case. The only overhead in using macro substitution is a time foxpro needs to process macro substitutions. It doesn't affect sql select itself. You wouldn't save time by spliting sql select "verticaly" as you mention at the begining of the thread. Also I think the code would be simplier because all you need is to build each part of sql select separatly. You can also combine some clauses that aren't big if you want.