Come on.

That's a bit like me saying to you: "I have four guys at my house to do some home improvements. Please tell me what they specialise in."

Clients don't generally execute SSIS packages - it's a server thing. But you could set up a SQL job to execute the package and then create a stored proc to...

What do you mean by 'access'? Do you mean 'edit', or 'execute', or something else?

Also, what do you mean by roles?

Alvin Ramard (10/9/2010)

---

I would normally say that you only ask one question per thread. In this case, you helped me a bit and now I only have to say...

Sounds like the source file isn't there any more.

Or the network drive mapping has changed, maybe. You'd be better off using a UNC path for your source file (after checking...

da-zero (10/8/2010)

---

Maybe you could try a script task to solve this problem. After you've created the file, you could open it in .NET and go to the last line to...

That won't work - it's the destination that's changing, not the source.

Quite horrible and a very unusual practice. I suggest you tell them it can be done only manually and...

Seems like we've both spent enough time doing this stuff to know what works, Mr One Million 😀

I'm with Alvin (as usual) - Script Component with multiple outputs to your various different tables.

Great - thanks for posting back.

Specify " as your text qualifier in your flat file destination connection manager.

Just because you update a variable when your package executes does not mean that the value of the variable will be persisted in the Variables window afterwards.

Try putting a script...

Does View/Error List give you anything useful?

Alvin Ramard (10/5/2010)

---

Phil, I'm not sure what you're asking? ...appropriately...

sqlusers (10/5/2010)

---

sqlusers (10/5/2010)

---

Leo Suresh (10/5/2010)

---

I guess you are using table variable inside your SQL query. If that is the case, then OLEDB source task will not generate the columns.

Use a...