Yes

I can see that is the simplest option. But give the web service a shot when you have time :-) its a nice intelligent way to pass communication around and it wasn't as complicated as I expected.

BTW Blats not a bad choice. I've seen it used in a few places.

>Looking to have a really low complexity level and fast turnaround, so the Blat option is looking better to me at the moment.
>
>>Jay
>>
>>just echoing Craigs note there.
>>
>>I set up a web service using foxpro dll and interop so I could wrap it in .net . It meant I could use existing code
>>
>>http://www.west-wind.com/presentations/foxdotnetwebservices/
>>
>>is a good article.
>>
>>having said that it was a bit of a problem releasing new dll so if you are getting your head round .net a pure .net web service could be the way to go.
>>
>>Nick
>>
>>
>>
>>>That's great. If that's the way to go, would someone please help me understand how to set that up on the server side?
>>>
>>>>Also, with web services, you can put the data directly into a database. No preliminary processing required.
>>>>
>>>>>The nicer thing (IMO) with FTP and Web Services is that you can confirm that what you send has been received. Also with Web services you can respond intelligently so your application knows that what it sent has not only been received but processed (or not) at the web server end. I often think that email communications are a bit like firing your messages off into the dark. thye may get there but you don't really know.