Re: File open
Dean,toggle quoted messageShow quoted text
I first implemented functionality in an application to limit each user to a single login by locking their username with Lock(User(0)) in a late service pack of v9.4, but it didn't really come into its current, fully polished state until v10.1. This same application is currently operating in uniPaaS v1.9o and has been tested and is ready to go in v2.5, when (if) they ever get a round tuit.
The thing is, the users of this system were and remain some of the least patient users I've ever encountered. They'd as soon three-finger an application as take a second breath; it's their go-to solution for anything. Really.
This has never been more of a problem than during their early wireless days. For more than a year, they struggled with a half-assed, DIY wireless network in their main warehouse, before they were finally convinced to cough up several grand and get the job done right. In the meanwhile, however, one needed only to sneeze to lose one's network connection, lock-up one's computer, and, as a result, often leave data in an inconsistent state. So I expended a great deal of time and effort fixing data anomalies and otherwise making the software as fault-tolerant as possible.
Moreover, I seem to recall hearing of at least one other house (FactoryMaster? AOD?) having problems as you describe, but, try as I might (and I have indeed tried) to produce such artifacts, I cannot. I even tried again just now, albeit for only a couple of minutes, but am still unable to cause the internal locking system to hiccup. I might be inclined to think that I'd done something extraordinary, but it's really not in the least exotic: I attempt to Lock the resource in the Main Program's Task Prefix, proceeding only if successful, and subsequently UnLock the same resource in the Main Program's Task Suffix.
It works for me; of course, YMMV.
At 05:59 AM 1/5/2017, you wrote: