CTRL+BREAK isn't working

[lisarmj]

I have recently upgraded to Access 2007 on Windows XP and switched from a PC to a laptop at the same time.

The database that I built in Access 2000 on Windows 2000 pro is running well on the new system, however it is still a work-in-progress and the code is not fully tested.

As a result, there are times when the code errors and a msgbox pops up stating the err.description as well as an OK button. This is fine (and as programmed) - however, I am am unable to stop the code to debug this problem. In the past, CTRL+Break was the answer...on my new computer (Dell Latitude D520) this isn't working.

Break is still located on the Pause Key however it is written in Blue (generally used for keys requiring Fn in addtion) - I have tried CTRL+Break as well as CTRL+Fn+Break but neither are working.

Does anyone have any suggestions? At this time I have had to CTRL+ALT+Delete to exit the program and this isn't how I want to work.

Thanks!
Lisa

 

[modest]

Have you tried just Fn + Break?

 

[RoyVidar]

Are you sure the only thing you've done is changing version?

You haven't by any chance disabled "Use Access Special Keys" in Tools | Startup in 2003- versions, or in 2007 Office Button | Access Options | Current Database?

This setting, I believe, also toggles the AllowBreakIntoCode property, check it out, and enable it, at least when debugging.

 

[lisarmj]

Are you sure the only thing you've done is changing version?

You haven't by any chance disabled "Use Access Special Keys" in Tools | Startup in 2003- versions, or in 2007 Office Button | Access Options | Current Database?

This setting, I believe, also toggles the AllowBreakIntoCode property, check it out, and enable it, at least when debugging.

I did double check the settings.. Use Access Special Keys is checked, in addition I have startup code that sets AllowBreakIntoCode to TRUE.

Modest...I did also try Fn+Break...no luck there either.

Thank you both for your suggestions, but I need to keep looking. In the meantime, I guess I'll change the error handling to prevent a modal msgbox from stopping the program.

 

[boblarson]

Just a suggestion but sometimes I've had to hold the Ctl+Break buttons down for several seconds before it senses it.

 

[pdx_man]

Did you convert the database to A2007? Make a copy and try this. You won't be able to go into debug mode of a previous version.

 

[lisarmj]

I'll give that a try...all I did was open the file and start working it seemed so seemless I didn't even think to take an extra step...to convert would you suggest opening a blank database in A2007 and importing all of the tables, forms, etc....?

I am working with a FE and BE - should I convert both ends or just the FE with the code?

Thanks!

 

[lisarmj]

One more quick question - I originally began developing this database in Access 2000, but the end-users will be using Access 2003. If I convert to Access 2007, how will this affect distribution to a prior version?

 

[Noel]

I've only taken a cursory glimpse at 2007, but I would think you should be able to convert up and down (tools>database utilities).

 

[RoyVidar]

> You won't be able to go into debug mode of a previous version.

Since you're not using any disclaimer/CYA on it, I must assume you intended to pass this on as "The Truth".

I believe this not to be correct

When removing project password and enabling Use Access Special Keys i can ctrl+break my 2000 format dbs and enter VBE to debug in all versions 2000 through 2007.

I think I see one difference between 2007 and previous versions, though, that in previous versions, you can turn off the special thingies in code when opening the app, while that doesn't seem to work in 2007. It seems you'll need to close and reopen, as is the message you'll get in the interface.