Half a dozen ways of doing the same thing isn't a bad thing... then we all get to learn something. "Fresh eyes" is what I call it.

I didn't know that setting the .Value of a command button is the same as clicking it (which I tested, and it seems to be).

I guess the only "problem" with cmdCancel.Value = True is that it won't cause a Compile error if the command button exists on the form, but you've forgotten to actually add the Click event. Obviously compile errors are "better" than run-time errors, generally speaking. But in this case, it would be pretty obvious at some point during development that you were missing something so essential to the form as cmdCancel_Click.