David R
I know a few things...
- Local time
- Today, 05:48
- Joined
- Oct 23, 2001
- Messages
- 2,633
No idea how to search this one due to the general terms involved.
Lately I've got a couple of code snippets that want to 'stop' running and highlight a line with the yellow arrow. If I hit F5 or F8 and step through it as if I were debugging, it works fine from there on until I close and reopen the database. It only seems to do it on fully automated code - for instance an email that is set up to .Display will run correctly, but one set to .Send will breakpoint.
Any theories? I only have seen this so far on databases where the Navigation Window is still visible (i.e. it's not locked down for production), but I can't release a database into the wild if it's going to freeze, my users will have no idea how to step through code!
:edit: Several days ago I DID set a breakpoint on that line (to keep from sending live emails during testing), and Access somehow had a ghost remembering that... letting it breakpoint once more and then Debug > Clear All breakpoints seems to have solved it.
Lately I've got a couple of code snippets that want to 'stop' running and highlight a line with the yellow arrow. If I hit F5 or F8 and step through it as if I were debugging, it works fine from there on until I close and reopen the database. It only seems to do it on fully automated code - for instance an email that is set up to .Display will run correctly, but one set to .Send will breakpoint.
Any theories? I only have seen this so far on databases where the Navigation Window is still visible (i.e. it's not locked down for production), but I can't release a database into the wild if it's going to freeze, my users will have no idea how to step through code!
:edit: Several days ago I DID set a breakpoint on that line (to keep from sending live emails during testing), and Access somehow had a ghost remembering that... letting it breakpoint once more and then Debug > Clear All breakpoints seems to have solved it.