I have made recently a entry in the VFP 9 wish list:

-----------------------------------------------------------------------
New SYS() Function to specify the scoop of undeclared variabled

Currently when using an undeclared variable, VFP creates the new variable whith a private scoop creating potential problem in MTDLL. Having a new SYS() Function to modify the default behavior so VFP creates all un-Explicitly declared variables with a LOCAL scoop would greatly improve Com servers stability.
-----------------------------------------------------------------------

I got bitten again with an undeclared variable last week, i spent days to find the cause of a C5 in one of my COM+ hosted DLL. The problem was :

LOCAL loCusror
loCursor = CreateObject("CursorObject")
.....

I fixed the loCusror to loCursor and the C5 went away. This kind of problem is very difficult to find especially when you have hundreds of programs being modify by many developers.

In VFP 8, The problem will probably become worst because we have so many great new objects like collections and Exceptions. What if i use a try - catch, and catch to loExeption instead of loException ? It will cause the variable loExeption to become private.

I have been told by some of the VFP team that VFP 8 is closed an no new functionnalies will be added. But this one would solve lots of existing and future problem.

I need to spend some time on coding application. Not debuging undeclared varables...

Please, Please, Please !!! If someone at MSFT is listenning, ( Jim, Mike, John....) If you can make this happend in VFP 8 i will pay you a beer at the next Devcon !