It depends on what you are using to interface with the Web Service and more importantly what the server expects.

As you know VFP arrays don't support named indexers, so if you end up passing an array that won't work. You can use collections, but VFP collections are not likely to be a workable parameter input to a Web Service call.

In general too, Web Services don't support named indexer's either. Web Services tend to serialize data into simple arrays. For example, if you have a .NET Web Service and you publish a collection or a dictionary into the WSDL it'll end up as an array.

Why do you need this functionality and why should it matter how you get the data into it? If this is necessary in your code why not create a collection internally and then turn the collection back into an array or something along those lines.

+++ Rick ---

>To consuming a Web Services, By parameter, I need to set as array's index a name instead of number, as described following:
>
>

>array('name'=>'new name of product'),

>
>In VFP, is that possibility, I mean... The possibility to contour this difference.. giving something to this web service that can be interpreted on its needs?
>
>Any help will be full appreciated..
>
>
>Claudio