Thank you. I understand.
>JSON stands for 'JavaScript Object Notation';
>it's a literal describing an object's properties;
>otherwise you'd use an array literal:
>
>[2,
>"F100",
>"AIR FILTER, 20x20x2",
>4.00,
>2.00,
>"FOOT"
>]
>
>
>>Hi,
>>
>>Is it a good practice that the json received from Web API by a VFP application (and/or .NET application for that matter) has pairs of "field description" and the value? For example:
>>
>>
>>[{
>> "Id" : 2,
>> "Code" : "F100",
>> "Description" : "AIR FILTER, 20x20x2",
>> "Price" : 4.00,
>> "Quantity" : 2.00,
>> "Unit" : "FOOT"
>>},
>>>>
>>Or it is better if json has no "description" element and only the data?
>>
>>TIA
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
