Enterring debug mode on computer without Break or Fn key?

[warmslime]

Is it possible or should I just use another keyboard? The on-screen keyboard doesn't work...



NVM, fixed, this helped me (delete this thread if you want)
http://en.community.dell.com/support...518/t/19430669

[CJ_London]

I was going to suggest using debug.assert to stop the code when certain conditions are met

https://support.microsoft.com/en-us/kb/161153

[ItsMe]

I was going to suggest using debug.assert to stop the code when certain conditions are met

https://support.microsoft.com/en-us/kb/161153

I like that explanation.

[warmslime]

This doesn't help me when I don't know where exactly the error occurs! (ie when using error handling with custom messageboxes)

[CJ_London]

it's not clear exactly what your issue is - if you are trying to debug then use option explicit in all your modules and use error handling. Must admit I've not tried developing anything using just a touch screen, so perhaps you do need to plug in a keyborard

[warmslime]

it's not clear exactly what your issue is - if you are trying to debug then use option explicit in all your modules and use error handling. Must admit I've not tried developing anything using just a touch screen, so perhaps you do need to plug in a keyborard

This is exactly what I'm doing. I use option explicit and I use error handling. This results in custom message boxes popping up in stead of the standard Visual Basic popup (the one with the debug button). So I can't see where the code failed without ctrl+break. Also I'm not using a touch screen, only a keyboard that doesn't have a Break button (I guess I didn't really mention it in the OP).

[CJ_London]

so temporarily disable your 'catchall' error handling, and/or set a break point and step through the code

[warmslime]

so temporarily disable your 'catchall' error handling, and/or set a break point and step through the code

Yes but I'm working with an example database that throws the same error messages on multiple parts of the code so I don't know which one called it. So pressing ctrl+break is infinitely easier. I was able to remap the key using a registry edit and I use ctrl+f10 and it works now.