>Indeed, I started working with a similar object like the one you propose but that only allowed me to work with new objects based on the
>expandobject-like class ( can't add properties to existing ones ) and did not offer the use of with..endwith constructors to create new
>members on the fly.

Hmmm... that should work. But in any case even if it doesn't you still could benefit from just assigning `CREATEOBJECT("nfDyn")` - then you can use either direct assignment or the constructor approach.

Either way this is really cool. I'm just really blown away I've missed this particular thing in all these years (THIS_Access()) because I've wanted to do this sort of thing myself for a number of things (that I now no longer remember :-)). Definitely can see it useful for user object contruction for returning as result values especially in service type application where I often have to wrap results into a service header object. I use ADDPROPERTY() for this today which is cumbersome although it works. For those use cases this will be perfect (ie. non-high perf impacts).

Again thanks for posting and giving me a few new ideas...

+++ Rick ---

>
>I use it basically to make dynamic changes to DTOs , so Vfp can do real message based communications with ease.
>
>Configuration objects, parameter objects can benefit too; but I'm rounding a definitive spec to get Intellisense to work with object constructor functions that make use of _()