IMHO if you turn off warnings your procedure should include an error handler that turns them back on. That, or use .Execute method of the database object.
When I see multiple objects with similar names I suspect they are just minor variations of the same thing. If they are, one object used in several ways helps keep db size down and reduce re-design work when changes are made.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.