We use Windows Services all the time with success. But we have to launch the 
server application from time to time as a desktop application as John said, 
but it is pretty rare. Nearly all errors we try to catch and write the 
messages to a log file. But there are situations where this isn't possible, 
e.g. starting with wrong journal file. These messages are generated by 4D 
processes unmanageable by programming or settings.
But there is a feature request that such error message should be logged all 
the time if the application runs as a service:

4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com

Reply via email to