>I have a macro substitution in an SQL statement as:
>
>SELECT &gcSelect FROM ....
>
>The SQL is bombing because the string being used in gcSelect is 391 characters long. Is this a limitation on macro subs in SQL or is this a limitation in VFP itself. I notice that if I try to evaluate the variable gcSelect in the debugger, it is truncated. Again, didn't know if this was a limitation on the watch/locals window or VFP itself.
>
>Any thoughts?
As Ed said test your SQL w/o macro substition to check if it really has someother problem (ie: forgotten having extra quotes around char expr).
It's hard to check in debugger I simply do a :
activate screen
? lcExpr
for checking.
Macro expansion limit AFAIK is 8192 which is also max. command line limit. But it's a lot :) I don't think your problem is the macro itself.
Cetin