Roy (and to Jeff H),
Honestly, like I said, it's a Hail Mary. I know Jeff wasn't responding directly to me, but he would know that PdxRbld uses TUtility of course. And I remember a company called Borland affectionately,
I have ALWAYS used the DBISaveChanges in AfterPost. It's even got a shortcut template for itself in Castalia. And the local Share requirement is part of my settings, always.
That said, DBIUseIdle in AppIdle is new to me. AppIdle I am familiar with. I use it to check to see if the workstation has been running unattended for two hours. At which point the program sends an email to the workstations department manager requesting he or she go over to the workstation and close things down properly. But using DBIUseIdle is new to me. If the suggestion is to check for changes or run DBISaveChanges for ALL databases during Idle moments, that's a no go. There's 230+ databases open across the various departments. I've looked at Dr. Bob's entry on this subject matter, but it's not clear to me how to implement it in a way that makes sense for each user. The average for any of them would be ballpark 30 to 60 databases open at a single time. I can't run a check for all of them, even if I could use the ini/registry to make it unique per WS.
Thanks for trying Roy. (and a shout out to Jeff Hambl). GM