the easiest solution would be to convert your data to XML that is readable by Excel: http://www.microsoft.com/office/xml/default.mspx

CSV data elements can contain commas if the data is quoted:

item1,item2,"lastname, firstname",item4

-Mike Gercevich

Without SQLs Client tools installed at the Client, the dts COM+ objects would not be available to the client machine compiling the VB source.  This solution will not work.

If you...

This has nothing to do with your DTS Package.  This is a SQL error stating that you do not have permission to execute xp_cmdshell.  Doesn't matter that you are trying...

Check the order of your parameters for the method call:

Package.LoadFromSQLServer ServerName, [ServerUserName], [ServerPassword], _

    [Flags], [PackagePassword], [PackageGuid], [PackageVersionGuid], _

    [PackageName], [pVarPersistStgOfHost]

All params are not optional, and will need to be nulled if...

it appears that you are attempting to load a structured storage file (.dts) with the LoadFromSQLServer method.  The package name appears to be a path.

-Mike Gercevich

Have you looked into using a FOR XML EXPLICIT stored proc to create the resultset in a XML stream.  With Active-X you could capture the stream and save it to...

If you can use some sort of crazy join on your ddq to get the same results... it would execute much faster...

If that is not an option, setup caching on...

Setup execution logging on your packages to log to SQL. The results of every execution will log to sysdtspackagelog and sysdtssteplog tables in the msdb database.

-Mike Gercevich

Since all tasks are derived from a Interface, the interface and assigned a type property to define the task reference.  There is no Me or This because it would be a reference...

If you are not executing multiple steps at the same time... your precedence properties are defined that there is a single path through the package.  You can look at the...

Using the Save As structured storage file (.DTS) offers the most flexibility by keeping the layout and annotations of the package intact.

There are other tools such as DTS Backup 2000 and DTS...

One of the problems I have found with using xp_cmdshell, is there is no good way to see if the package is currently executing or not.  I have found that...

Do the Event, SQL or Job logs point to any reason for the failure to load?  What is the error message you are receiving?

-Mike Gercevich

Try PRINT STR(@HR) after each line as well as running a trace under profiler.  That should give you a better understanding of what is going on from the servers point...

I'm pretty sure that this is not the correct syntax for the sp_OAMethod call to load the package:

EXEC @hr = sp_OAMethod @oPKG,