First question in a series of posts in fool-proofing a workbook:
Right now I'm trying to create a "login" through excel. I've gotten as far as making a form with username and two passwords, and relatively short code so that it's hopefully executable before a user can do anything.
Nonetheless, the ESCAPE key seems determined to enable my procedure's downfall, despite my attempts to stop it from doing so.
Here's the code I've wrought so far:
Note the .EnableCancelKey is disabled and on hitting ESCAPE nothing should occur, yet especially when the procedure is working on the Workbooks.Open statement, the ESCAPE key fails it and the common error/debug message occurs. I have not encountered this problem anywhere else in the code (like I said, it's short enough that there's no time for someone to hit escape), but I can't help but feel that this error would occur similarly otherwise.![]()
Please Login or Register to view this content.
Any suggestions on making the Unbreakable Procedure would be greatly appreciated!
Bookmarks