Access 2003. I removed all references except the Access, VBA, and DAO
references, as these were the only references needed once I commented out
the ADO code. I didn't remove the other references for any particular reason
other than habit - I'm just in the habit of always removing any reference
I'm not using.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.


"Boris" wrote in message
...
Brendan Reynolds wrote:
Well, you've got my curiositly going now! So I tried changing the code
behind the command button as follows, (I've left the original ADO
code in there, but commented out) and sure enough the error
disappears ...

Brendan, I just tried your code and still get runtime error 3021!
Replacing
ADO code with CurrentDb.Execute calls doesn't help me. Which Access
version
do you use and which references did you set?

Boris

[...]