![]() I've had similar situations where typing in the same code again exactly as it was before, but after deleting the original and offending line, has resulted in the problem disappearing and all being hunky-dory going forward. ![]() The problem is not with any of your code I'm confident to say, but probably something you've done earlier, or that Access has mistakenly tracked you as having done earlier. ![]() Then I close and reopen the database and hope that the problem has disappeared. What I try to do (if I can attempt to put some ideas into a coherent set of steps to try) is to make a change to the code (Nothing that has any real effect, but enough for Access to realise that a save is required) then, assuring that no lines are breakpointed anywhere, compile then save the module again. When I get something like that I have to play it by ear to a certain extent. It certainly makes more sense Lori, but as I said earlier, this error message is largely unhelpful. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |