Solved Breakpoints don't work?

bob fitz

AWF VIP
Local time
Today, 08:08
Joined
May 23, 2011
Messages
4,806
Can anybody please confirm for me that it is usual/expected behavior for breakpoints to stop working after unticking the "Use Access Special Keys" setting?
 
Hi Bob

Didn't know if it did or not so just tried it and you are correct the Breakpoints do not work after unticking
 
Hi Bob

Didn't know if it did or not so just tried it and you are correct the Breakpoints do not work after unticking
Thanks mike60smart, for confirming that. I've never noticed this until today when I was trying to debug some code in an app that I thought was ready for handover to the client.

To be honest I wasted several hours and suffered a large portion of anxiety, thinking at first that perhaps something had become corrupt.

It's nice to have it confirmed as usual behavior. Thanks, once again, for your interest and help.
 
Hi Bob
I'd never noticed it before but can also confirm your findings using both A365 and A2010
However, I'm not convinced this should be treated as 'normal behaviour' as, at first sight, I see no obvious reason for there to be any link
It appears to be a bug and I will alert the Access team about this and try to find out whether it can be fixed
 
Last edited:
Hi Bob
I'd never noticed it before but can also confirm your findings using both A365 and A2010
However, I'm not convinced this should be treated as 'normal behaviour' as, at first sight, I see no obvious reason for there to be any link
It appears to be a bug and I will alert the Access team about this and try to find out whether it can be fixed
Hi Colin

Thanks for your input and interest.

Like you, I could see no reason for any link which was why I thought the form or one of its controls may have become corrupted. After finding the same behavior in a new db I began to get concerned about my installation of Access itself which is what prompted me to start the thread.
I should be interested to know what response you get from the Access team.

Thanks, once again, for your interest and help.
 
Pleased to say I had a response from MS within 6 hours. They have also been able to reproduce the issue.
They have given me an initial assessment and will be investigating further.
I wonder how long it might take them to change it
P.S. Not sure why you marked this as SOLVED!
Because my question, about how Access behaves, had been answered. It might not behave as we may want/expect but my question was really about finding out about other users' experiences.
 
I wonder how long it might take them to change it
That's a very good question. Some bugs are fixed very quickly. Others can take years!
It partly depends on how important the bug is but also on the degree of complexity. The monster bug is still not fixed after approx 4 years!
I'll let you know more when I have something else to report
 
Thanks for posting here Shane. I had forgotten to provide the update despite my promise in post #8
 
Well this is good to know since I'm already on version 2307 and was not seeing the problem.
 

Users who are viewing this thread

Back
Top Bottom