well, i think the issue's in the procedure you are talking about ...i don't think it's schema aware;
i wouldn't take the error message from the scheduled job literally(that a slash exists in some object name)
if you post the procedure, we can help make it schema-aware , which i'm sure will make the error go away.
Lowell
--
help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!