2 approaches - wiether a simple exe scheduled by the windows scheduler, or, start with a Service - depending on the other requirements, eg timing, I might use Quartz.Net, definately a logging layer, and maybe some way of communicating with the service for status info
Thank you all for the feedback. I'm going to read up on Windows Service applications to see if that will do the trick. I am working with a SQL Anywhere database.The application will consist of logging into the database and running a procedure at a predetermined interval.
If it's a cross domain issue (and see other posts - suspect not), then there's nothing you can do on your side....the owner of the service / site needs to accept the correct headers (AccessControl-AllowDomain etc).
If this service is intended to be called externally, then they must have added them already though!
C# has already designed away most of the tedium of C++.