Hi Christopher,

>I have found that calling the function within the FLL that calls _GetObjectProperty in a loop will cause _GetObjectProperty to error out. I can consistanlt error out at loop iteration 511 with error: "There is not enough memory to complete this operation." Is this a known bug? I have spent the better part of today going through MSDN.

At least to me the error is not known, but that doesn't mean much... There are a number of things you should be aware, however:

a) Microsoft takes down KB articles when the product is not supported anymore and probably on other occasions, as well. In most cases, this is not necessarily bad because you don't have to wade through bugs that have already been fixed. On the other side, however, the VFP API is pretty old and a lot of the bugs in there are only available in older versions of the KB. If you know someone who has a 1997 TechNet or MSDN Library installed, you might be able to find more bugs and explanations about writing FLLS, because the majority of VFP 3 articles was still in there at that time.

b) The VFP API has only been marginally updated since FP 2.5. While I wish it would be different, the VFP API and FLLs are not a top priority anymore. That started to stop when "full" DLL support was added in VFP 3. And with the move to COM and now to NET, a FLL is a technology that is by two versions outdated, hardly used and unlikely to get updated. IOW, if you find a bug, you need a work around. And unless you really have to access functions in the VFP API, you should consider writing a COM server. You can pass any VFP object to a COM server and it is automatically wrapped up for COM. That means, you can access any property without much difficulties and often even without a major speed decrease compared to a FLL.

Christof