Bill; It *should* be checked on the write. From the time it's opened to the time the write occurs circumstances might well have changed. For example, a long running processes (like our overnight run) can start and open files which are fine. As it runs the O/S backup routine starts to run and locks the file at the OS level. UD will error out on the write as it does not have permission, at this point, to write to the file.
Of course, with the belt and suspenders approach you should check it on the open so that if there is a problem it doesn't go half way through a routine before discovering it's unable to make a write. Hth Colin Alfke Calgary Canada -----Original Message----- From: Bill Haskett Is this discussion identifing a preference to manage permissions at the front end (OPEN) instead of at the back end (WRITE) in a BASIC program? Has anyone resolved this question and come up with a general preference one could use as a "Best Practices"? This knowledge would be welcome when trying to retrofit this functionality into a current application. Bill ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
