Either turn off warnings before the loop then back on again after it, or use the Execute method of the Database object, which does not prompt. If you use the former, you should ensure that they do not get turned off permanently, otherwise bad things can happen without the user's knowledge. I seldom turn off warnings anymore, but if I do, the procedure has an error handling routine that ensures they are turned back on.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.