Only one possibility here, I'm afraid. Figure out what's causing the
error, and change the macro or the database so it doesn't happen
again.
Other than that, using a VBA procedure instead of a macro may give
more flexibility in managing the error.
- Steve Schapel, Microsoft Access MVP
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
