That's odd.... It would seem to me that checking out the program would check the write permission on the file; therefore, Unidebugger would respect that.
Are the file permissions being modified by the "check out" process? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gordon J Glorfield Sent: Monday, January 31, 2005 4:13 PM To: [email protected] Subject: [U2] Unidebugger Speaking of the Unidebugger and Sarbaines/Oxley, we are having some issues here with them. Currently our green-screen editors are front-ended by a subroutine that checks a database to make sure you have the program "checked out". If you don't have it checked out the editors die with an error message alluding to a security violation. Unidebugger does not honor the "checked out" status of programs in our library. Is there a way to add this check to Unidebugger? Gordon J. Glorfield Sr. Applications Developer MAMSI (A UnitedHealth Company) 301-360-8839 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
