Here are the "mini-RDBMS" functions I'm talking about that made me think that VFP would run well as a service. Comments?
1. Sleep (via the API to not soak CPU?) for 5 minutes and then retrieve some remote data and then work with it.
2. Sleep (via the API to not soak CPU?) and wake up every hour to see if it's 2:00am, and if it is kick users off of tables and do re-indexing and etc.

Is it even possible to run a "faceless" VFP app using srvany from the NT Resource Kit? And if it is, would each service load seperate instances of the VFP runtime DLLs or would they share (thinking of RAM usage here)?

Thanks.


>It's not well-suited to the role, and the money spent in creating something with VFP that really delivered similar capabilities would far exceed the cost of buying something that was designed as a backend. IOW, you could kludge something up, but it wouldn't do as good a job, and more than likely would exceed the cost of using standard backend products, which generally offer features that VFP's native file system can't furnish.