Hi,


>>
No problem, I think for this kind of need, a more generic approach should be used. In my case, I still kept the original XML Web Service approach, for application that wouldn't have big tables to transfer, and another approach to transfer by FTP, for big tables.

Basically, it's generic. I provide a configuration file that for each table we have the choice of telling which kind of transfer we want. So, if we know that a table is big, we can have the transfer to be done by FTP. But, everything is controlled from the Web Service. There is a method IsTypeXML(() which return if the required table should be transfered by XML or by FTP. If FTP, the Web Service has another method GetFTPPath() so we know the parameter for the FTP transfer.
>>

Just a thought...
It I understand correctly you now need two round trips to the server to get XML results and three trips for FTP. Would it be better to return a slightly more complex result to the initial call? If XML is OK then return the required XML; if FTP is required then return a different XML message containing the FTP path. Maybe use an attrib in the XML root to indicate the type. That would ensure the XML got there in one call, FTP would take two....

Regards,
Viv