Field data Assignment

[Elon Close]

Thank you Dave for the pointers!

I know that a variable is simply a static location from which and  
into which data is put. A ShortCall can use all the variables  
declared in the containing procedure. I also tend to declare  
FileGlobal and Global in any procedure in which they are used, though  
once declared that is not necessary. Just left over from other  
languages, and a way to keep track of what is available.

A Field name is a dynamic item, it has to fetch and store in a  
"movable" storage location, the current, active cell. That Panorama  
correctly does that, even when the name is fetched from a variable's  
storage location is quite impressive. I thought it might know enough  
to realize that when the item in the storage location was a Field  
name, it would do what it had to do. Obviously, a variable is a  
simple storage location, period. To store in a Field something extra  
is needed that can do the dynamic processing, eg. the Cell, or Set  
commands which I missed seeing, or looking into.

So once again, Thanks Dave, and a Gold Star to Panorama for having  
the tools.

Elon
erclose at dakotacom.net

As usual I didn't look deep enough and panorama had the tools.
On Feb 6, 2008, at 7:24 AM, David Thompson wrote:

> Nothing will turn a variable that isn't already
> local, into a local. What lead you to the
> conclusion that this was happening?
>