Drag 'N' Drop is your...

Unfortunately you can't set it to auto-fit. Best you can do is to layout the columns in the report to accomodate the data as best you can.

Also, if you haven't...

I thought that's what stored procedures were for

Why do you use a custom logging table instead of the sysdtspackagelog table ??

Yes this works well for multiple tables where the structure is the same. If you try the same approach with tables that have a different column structure without modifying the column...

Create a DTS package that copies one table. Then save this package as a VB file. Take a lokk at how the transformation and column mapping are done. You'll need...

Check the FAQ on setting connections over at http://www.sqldts.com

Or for something completely different, you could turn on the inbuilt SQL Server Package Logging. This logs package/step/task execution to tables in the msdb database. From there it's a simple...

You obviously aren't following the installation instructions

That was it. Ta muchly.

Isn't parsing and validating something that's done on the client, or business layer? What is the client application developed in? Does it understand native date and time datatypes?

You are aware that using the Data Driven Query task makes the Datapump work in row-by-row mode?

It would be much more efficient to bulk-load the data straight into a staging...

Use DTS to import into a staging table. The run appropriate insert/update/delete T-SQL statements to update the production table.

For inserts, you would left join from staging to production and insert...

Ok, then before you come to a SQL Server forum to get help about an error, how about you visit a VB.Net forum to get help about how to use...

In the Transformations tab of the datapump task, select the source and destination for the date column only. Then create a DateTime transform. This will allow you to specify the...