You can create a program that has no forms and runs as just a timer-event. When the event fires it can execute a function to check for whatever you need to check for and handle that situation for the user.
You can also create it as windows systray item. This way the user could right mouse click (providing you allow them to do that) and kill the process, run it mannually, etc.
instsrv.exe with srvany.exe is a viable option, look them up on the web using a search engine. I tend to use Installshield professional and the NT Service object that it provides for my install set.
Slighthaze = NULL
[ul][li]FAQ184-2483 An excellent guide to getting a fast and accurate response to your questions in this forum.[/li][/ul]
Slighthaze: Does this mean that you have distributed VFP programs to be installed as services?
Have you had any issues with them? (ie. VFP system UI dialog boxes that may be difficult to suppress, etc)
Do you see any benefit to running a VFP program as a service instead of as a normal, yet 'invisible' application, started, say, through ( Start Menu -> Programs -> Startup ) ?
Does this mean that you have distributed VFP programs to be installed as services?
Yes, however the service(s) was usually just a small part of a larger application.
Have you had any issues with them?
No, nothing too major. Usually a little more time and hassle than with a normal application.
Do you see any benefit to running a VFP program as a service instead of as a normal, yet 'invisible' application, started, say, through
This truly is the question I believe a developer should be asking themselves before creating a service. There is only one reason that I have ever found for creating a service as opposed to an invisible application called from a registry run key or the startup folder...and it is if you require your application to continue running even when the users are logging off and on (switching users). There may be some other really good reasons, but I have not found them as of yet, and prefer to use an "invisible" application if this is not a requirement. NT Services truly are for that other .01% that an "invisible" application cannot accomplish.
Slighthaze = NULL
[ul][li]FAQ184-2483 An excellent guide to getting a fast and accurate response to your questions in this forum.[/li][/ul]
Good points: I think your post will answer many peoples questions... I forgot that services ran independantly of the logged on user, which could be essential for some VFP server-side apps.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.