First, Let me say it has taken 10 years to get back to where I could post on this forum. Before then I was a regular poster (more questions that help). Not sure if anyone is still here that used to post regularly and that helped me over the years but if they are I want to first say Thank You. For 30+ years now I have an app that I developed and maintain. At some point many years ago I made an attempt to shutdown my app when users stay logged in for hours and days. I really need to reindex and things like that overnight. I do have users legitimately in the system 24/7. I am revisiting this issue. My question has to do with an overall concept. I have decided in order to close my app on inactivity, it really has to be context sensitive, in other words, it depends what the user is doing. For example, a user may be adding a record in one of the data entry screens. If that is the case, I would need to release the views/cursors, etc that are in use at that time and THEN quit the app. At the same time, that makes doing the shutdown a lot more complex because my app has over 100 tables and 1200 views. I am asking if I am making this too complex? All thoughts appreciated.
Red Flag Submitted
Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Tek-Tips forums is a member-only feature.