Quote:
Originally Posted by fumei
AGAIN, though, it is a very very simple thing to open up the VBA editor, see the above code and...delete it. Boom. then delete any existing variables. Boom. Gone.
|
Indeed, the whole scheme will be defeated if the user has their macro security set to 'high' or doesn't allow the macro to run. It also relies on the cheater using the accomplice's document as their own. Students will soon wise up to the security when they find they're being prompted to save changes to the document after having done nothing more than opening it. Although you could add code to save the document immediately the variables are updated, the change in the file's date/time stamp would be its own give-away.
Gerry's approach will also be defeated if the cheater simply opens a copy of the accomplice's document to copy content from, pastes it into their own document, then deletes the accomplice's copy after closing (which is quite likely).