Phantom breakpoints in VBA
Don't know if this is any help or even the same thing.
https://stackoverflow.com/questions/215 ... een-halted
https://stackoverflow.com/questions/215 ... een-halted
Does your code compile fine.
I've had points where I've compiled stuff (more so in access) where the routine becomes corrupted
Try commenting out the line of code where its hitting the breakpoint, then compile. Uncomment the line of code and then compile again
I've had points where I've compiled stuff (more so in access) where the routine becomes corrupted
Try commenting out the line of code where its hitting the breakpoint, then compile. Uncomment the line of code and then compile again
Cheers, I didn't even realise there was an option to compile on the debug menu, I thought Access only compiles on demand. I'll give it a try if it happens again.ODPaul82 wrote: ↑Thu Apr 22, 2021 8:36 pmDoes your code compile fine.
I've had points where I've compiled stuff (more so in access) where the routine becomes corrupted
Try commenting out the line of code where its hitting the breakpoint, then compile. Uncomment the line of code and then compile again
Access is awesome, wrote an alternative to SSIS using it when IT wouldn't let us get hold of a SQL Server instance
Another thing with your compile error, where I've had the routine entirely corrupt before after compilation, what I did to fix was comment the entire routine out (rather than the individual line of code like I said before), take a copy of that code block and uncomment it then do a find & replace to just add a prefix or suffix to the routine name then re-compile.
Another thing with your compile error, where I've had the routine entirely corrupt before after compilation, what I did to fix was comment the entire routine out (rather than the individual line of code like I said before), take a copy of that code block and uncomment it then do a find & replace to just add a prefix or suffix to the routine name then re-compile.