JayJay: Neither one of these verbs are invoked if someone logs onto an account and goes directly to TCL (no menu desired). For instance, one creates a UO account with Q-Pointers, ON.ABORT, and a few other things to allow extraction of data. :-)
The two functions you refer to are accessed, I believe, either via a BASIC error or a debug error. What I was referring to was D3 validates a user "at TCL" (and "at debug"). This way, the developer doesn't need to worry about all the ways this could happen, just that it happens. It doesn't matter whether it happens in the Unix or Windows implementation. Since I'm nowhere near as knowledgeable as I would like, I'm hoping I can find a solution to this sticky problem: from within U2 (and not from Unix this way and Windows that way), how can I guarantee only those I authorize, in the manner I authorize, can access resources? Along with "UOLOGIN" this information will always help. Thanks. :-) Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Jenkins Sent: Wednesday, June 01, 2005 1:01 AM To: [email protected] Subject: RE: [U2] Uniobjects hack ON.ERROR ON.ABORT (and remote verbs) JayJay <snip> It's funny. D3 has the capability to assign a macro to any user who gets to tcl (or the debug prompt). Often this macro is either a login (again) or a logoff. Works great. U2 doesn't seem to have addressed this issue because their client base has never required it. Hopefully, now they do! Bill <snip> ------- 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/
