Maybe you have a trigger firing that calls it? Or hitting an error in code that bounces the current line back above where the insert happens initially? What happens if you put a stop or exit sub right after the proc call in the code?

Andy

http://qa.sqlservercentral.com/columnists/awarren/