Ed -
Here are the questions I deferred from the Pointers on Pointers session on Wednesday. There are a bunch of them, and I would have privated them to you, but the suggestion was made that if they are public then everyone can get the benefit of your response. So here goes!

1) So a callback is a pointer to a function, and VFP can't use them even with CLSHEAP because we can't CopyTo(MyFunction). As a practical matter, what kinds of things does that keep us from doing?

2) What made you decide to add new methods AllocBLOB(), AllocString(), and AllocInitAs() instead of adding properties or parameters for Alloc() to use?

3) In your implementation of those methods, you don't always check the return value from Alloc(). Can I infer from this that it's very rare that Alloc() has a problem allocating space?

4) Would a CopyStringFrom() method be useful? This method would be a CopyFrom() that stopped when it reached a null character. (This is not an enhancement request <g>. I'm just trying to get a feel for how to use the existing functionality.)

5) In general, what is the "scope" of the DECLARE...DLL statement - just the current method/procedure? Or is it basically DECLAREd in some public VFP function space? If the latter is true, do repeated declarations take up resources unnecessarily?

Thanks for your time!
zahid