>>We have a need to receive error reports (either a table or text files) from all of our apps that are out in the field back to our home office. These are a couple of scenarios and questions I have regarding that.
>>
>>Email: What if the client does not have Outlook installed (some don't). What if they are using an email other than Outlook. Or don't use client email?
>>
>>Web Service: I now know how to communicate to a server, but what needs to be done on the server to accept the request/information?
>>
>>FTP: Have no idea how to implement this from either side.
>
>Take a look at incorporating Blat into your app to send what you need. It's very simple to use, is free, and works great. It runs straight from your program so doesn't require Outlook. I implemented it at my last client (on Bill Kuhn's recommendation) and it was a big hit.

The only case where BLAT will not work is where the client does not have access to an SMTP mail server - this is almost never the case but it is a possibility (like if your app is running on a laptop using hotel wireless - that may be a serious issue).

In that case, FTP can work although it is somewhat complicated to set up the FTP server, security, and processes to automatically grab the FTP file and/or notify you that you have one. It is do-able.

A sneaky way is to use SQL Server Database mail
- make a dummy database (easy)
- configure database mail at the SQL server (easy)
- add a stored procedure that takes your error info as parameters and sends email to you via database mail
- change SQL port to something way different to keep hackers away. You may want a seperate instance of SQL for this.
- have your app connect to the SQL server and run the stored proc when error occur (you may have to handle batching the errors in case no connectivity)