the.hoarse.whisperer
New member
- Local time
- Today, 19:55
- Joined
- Jan 12, 2013
- Messages
- 6
Have any members experienced this happening.
You change some code in a main module function. Then when you step through it in debug it starts jumping lines of code and going to called routines that you have just changed the code to stop it doing. Clicking on a variable to see the value produces nothing.
The way I have got round it is either by 'copying' the function into memory deleting the code and then re-pasteing it , or importing everything into a new mdb file. I use MSACCESS 2003.
If this is a common problem and REPAIRING doesn't fix it I'd be interested to know what other people do to fix the problem.
You change some code in a main module function. Then when you step through it in debug it starts jumping lines of code and going to called routines that you have just changed the code to stop it doing. Clicking on a variable to see the value produces nothing.
The way I have got round it is either by 'copying' the function into memory deleting the code and then re-pasteing it , or importing everything into a new mdb file. I use MSACCESS 2003.
If this is a common problem and REPAIRING doesn't fix it I'd be interested to know what other people do to fix the problem.