>Hi Dragan, the whole problem comes from the thought of
>needing to serialize any other type of objects different of
>data transfer objects ( DTOs in VFP = empty-based objects )
>
>Although is possible to serialize forms for example,
>it's out of the scope for some of the reasons you expose.
My point was the whole serialization/deserialization operation was unnecessary in this specific case (pass object by value inside one single VFP process) because direct cloning accomplishes the same without the overhead. But yes, when it comes to passing objects or object-like structures between processes, I love json and use it a lot.
> Json will find his way in VFP now that SQL server supports it
>( thanks to a fellow-countryman of you Jovan Popovic !)
>
https://blogs.msdn.microsoft.com/jocapc/2015/05/16/json-support-in-sql-server-2016/#comment-405This is great news - albeit probably too late for me. By the time my customers have SQL 2016 in sufficient numbers, I may already retire :).
