Robert,

It would be worth the effort to create all future programs that way, from a design standpoint. What Craig is saying is that it may break your current system, if you currently are using those private variables in procedures where they are not created (below that level). It may cause you to have to refactor a lot of code (which could be a good thing).

Make sure you have a backup, and give it a try...

>I should have been more clear.
>Would it be worth the effort to replace PRIVATE ALL LIKE l* with
>LOCAL labc,ldef,lghi,ljhk etc.
>
>>You can't do LOCAL ALL LIKE t*. You'll get a syntax error. Also, if you have called procedures that rely on a PRIVATE variable from a calling procedure, you'll get errors because the variable won't be found.
>>
>>>I have an application with many, many procedures and ALL of them issue this command. Would it be worth my effort to change these to LOCAL. The app is very speed sensitive.
>>>
>>>Robert