Quote:
Originally Posted by j.p.s
Thanks, that's a good suggestion and I will consider giving it a try.
Shouldn't exiting KUAL generate a close event and shouldn't that already trigger an access time update? Is this a kindlet vs booklet thing, an amazon bug, or a missing piece in KUAL?
|
Perhaps I mis-understood what you wanted to achive.
Closing KUAL **should** make it the most recently used already.
I thought you wanted to prevent the opening/closing of anything else from moving KUAL from "most recent" position.
So where ever the system records how recent something is used, the stored procedure should modify that field for KUAL, for anything opened/closed OTHER THAN KUAL.
(Don't want to loop when changing KUAL use time (whatever it is named) by letting it trigger the procedure again.)
I admit, I am not looking at a Kindle db at the moment and not even I trust my memory (which is why I no longer answer questions).
In fact, I am going through my stack of Kindles, looking for the one with the sql stuff on it.
It is here, somewhere. ....