>>vfp has quite a dose of prototypical behaviour if compared with a more strict class based language like java...
>
>can you expand on that? not sure I get it ...
>thanks

you got already enough, but my POV was mostly along Christoph's argument of creating a template on first instantiation, then copying from that - having a property set to datetime() will give you always the time of first instantiation, not running the function on each createobject().

We know that behaviour so we call code to set dynamic properties in methods without thinking, but that is a prototype behaviour in vfp ;-)