Does sound odd....

Check the fixpacks that you have installed

~PD

Any specific reason why it HAS to be a SQL command from variable?

Sure its possible to do, I have one that runs peaches, but there are different ways.

For example either...

You can update the variable with a rowcount transform.

Or if you want to get more funky with what you do (i.e. you want to count and then validate and the...

Try and disable package validation.

Every little bit of gained juice will help you

~PD

Awesome post Brandie...

Make it a FOR EACH ADO enumerator, and read your mini and maxi variables into here

Rgs

~PD

Merge join or lookup

Same like you did for the first sheet.

Variable var2SheetName = "16082008"

Change the variable with a scripting task

Remember that you will need a connection manager per layout.

Therefore, if sheet 1 looks different to sheet 2, you will need 2 different connection managers to handle this.

The rest is...

None that I can think of, but I wouldnt consider inserting using a linked server if I had a proper OLE DB option at my disposal

Readup in BOL on package logging.

This will provide you with a detailed error message which you can use

If the destination is a linked SQL server, why not simply use an OLE DB destination with your userid and password?

Add package logging. This will assist you to troubleshoot the error within the package

~PD

Yes, the environment variable will dictate to SSIS where the actual configuration table lies, plus any connection information required (i.e. userid and password).

hmmmm, suppose we have the following:

a) varRunType. varRunType...

I am saying that the environment variable will tell SSIS where the configurations reside.

The configuration filter will tell SQL what to load (i.e. configuration filter "MartinsDBConnectionString" which points to "MartinsDB"...

I received the same error when I changed the security of the package to "Dont save sensitive".

Fixed this by changing it to save with password.

One question though? What kind of...