The UniDebugger doesn't use locking when it reads/writes host Basic programs as this would not fit the home-grown check-in/out systems many people use.
In the wIntegrate Editor we added the ability to call a custom subroutine at the usual points which give 100% control, in the same way as the "service subroutine" which is optionally called by the Query Builder to filter what the users sees and does. However today the UniDebugger does not support custom host subroutines. -----Original Message----- From: Gordon J Glorfield [mailto:[EMAIL PROTECTED] Sent: 31 January 2005 21:13 To: u2-users@listserver.u2ug.org 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 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.3 - Release Date: 31/01/2005 ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
