I have used execscript() extensively is the past and can not recall any limitations with execscript. I assume what is happening behind the scenes is that VFP copies the code to a temp prg and compiles it and then runs it so if you can compile and then run it it should work.
Are you sure there are no hidden characters in your memo field that could cause problems?
Have you tried to add wait windows or messageboxes or log to a file to capture what line of code is the problem. After you have nailed down the line of code that causes the syntax error you shold be able to solve the mystery.

Let us know what you find.

Einar

>I have a table with a memo field. The memo field contains code to execute. When I run ExecScript(TableName.MemoField) I get a syntax error. The debugger won't show any code when I am running ExecScript() so I can't see the problem.
>
>However, if I do exactly the same thing except I copy the contents of the memo field to a .PRG and run that instead of the ExecScript(), everything works perfectly with no errors.
>
>The Foxpro help file mentions no limitations of ExecScript() although there must be some. In the script, I call database stored procedures. Is that it?
>
>Any ideas or wisdom to share?