Hi Ed,

>I'd like to see STRUCT use the same memory management API calls that CLSHEAP does and similar data conversion tricks, to eliminate the need for the external file that has to be distributed with STRUCT

The current version does. But since I made some more significant changes to the tool, it's not yet in a releasable state. But if anyone is interested in a replacement for the Convert.FLL, just let me know, and I send it or upload it here. It's only a few changes that are necessary to incoporate it into the currently released version.

>Neither STRUCT nor CLSHEAP handles low-level pointers and structures as easily or quickly as languages with native pointer support

Definitely not. STRUCT creates one object for every struct member, one for the structure itself and one object for memory handling. I wrote an application that had to create more than 200 structures (maybe 2000 objects in total for these structures), and loading them takes a while, around 10 seconds on my machine.

>and coding to use them would be relatively painful compared to C, at least for me.

Well, when using the STRUCT class, you don't have to do that much more work than writing this in C or something, but it's really slower.

When using my class it must be clear that this class is intended to offer the struct data type in VFP for occasional API calls. If the entire application contains only of API calls or speed is an issue, VC++ or Delphi is clearly the better choice.

Christof