>>>Hi Ed,
>>>
>>>>but isn't there a part of the VFP API that allows you to execute a VFP command from within an FLL? If all else is being uncooperative, you might try to access DIMENSION that way.
>>>
>>>_Execute(), yes, but wouldn't that require that you know the name of the array?
>>
>>You should be able to find it; it's got to exist in the NTI somewhere (I'm guessing here, guys, take anything I say as conjecture). Failing that, another approach might be to add a parameter with the name, to be used as such. But there's got to be a way. From a long time ago, parameters are either a value structure or a locator structure; if it's a locator, you have to do something to get to the value, there's an offset into the name table as one of the members, and there has to be something in an NTI entry with the name of the variable...
>
>
>Hello Ed!
>
>You are absolutely right! But which VFP API gives back the name of a variable for its NTI?
>When you pass an array by reference, you get the NTI of the variable, you can acces its element by this, or, if you pass a normal variable by reference you also get its NTI and then you can acces its value, but I donnot know any function, that gives back the name of a variable for its NTI.
>There is a _FindVar function which gives back the NTI of a variable for its name. Where is the opposite function?

Sorry, I really don't know; I was making an assumption based on stuff I'd done a long time ago with .FLLs, and I haven't really stayed on top of how they work now for a couple of years. I'll try to see if I can find some code that finds the base of the NTI, so that the offset in the locator structure can help find the right entry.