>WOW...
>
>Thanks a lot Randy!!! This is great feedback..
>
You're more than welcome. Reading some of your further posts (about data approach), I'm looking forward to it even further.

In the API section, I would like to see a little bit about programming strategy and practices WRT using the API. For example, in looking at your UUID example, you use two DECLARE statements and then at the end CLEAR DLLs. To me this raises a few points.

It seems every example I see includes the DECLARE statement right with the functionality. But is this always best? What is the performance cost of issuing a DECLARE statement? If you know that you're going to use a DLL call alot in your app, is there an advantage to DECLARE'ing it more globally in the app? If so, then the use of CLEAR DLLs would become as much a no-no as all the other CLEAR commands.

Let's say, for example, I start using XML alot in some applications. I purchase a C library of fast XML string manipulation functions. I intend to use these functions liberally throughout lots of classes of my apps. Would performance be alot better if I declared them just once? Is it worth it? OTOH, if I'm bound to encounter rogue routines that CLEAR DLLs, I can't afford that approach, even if it would buy me something.

Maybe these are non-issues, but I've never seen development strategies and proactices discussed when it comes to using the API, and at least for me, it would be nice to see.

-- Randy