D
dbeavon
Guest
>> I believe you can use the STOP-AFTER block modifier to do this in code. Yes, that is along the lines of what I need. But it seems better to manage this at the database level, since STOP-AFTER is sort of "hit-and-miss". Also that feature requires the addition of explicit code into every appserver entry point that has a potential to be long-running. I'm pretty sure that STOP-AFTER is a feature of the ABL-client-session, rather than a timeout which is enforced by the remote database server. (IE. my understanding is that the way it works is analogous to a bot that would push the the ENDKEY button after a predetermined amount of time, and then cross its fingers. There is a KB that describes various scenarios where the STOP-AFTER behavior would not work reliably.)
Continue reading...
Continue reading...