In the Copy Task of the DTS the procedure is as below:
Public Sub Task_Sub2(ByVal goPackage As Object)
Dim oTask As DTS.Task
Dim oLookup As DTS.Lookup

Dim oCustomTask2 As DTS.DataPumpTask2
Set oTask = goPackage.Tasks.New("DTSDataPumpTask")
Set oCustomTask2 = oTask.CustomTask

oCustomTask2.Name = "Copy Data from tb_vf_DAST_BUY_close
to [vfdevelop2].[vf99uat2].[tb_vf_DAST_BUY_close] Task"
oCustomTask2.Description = "Copy Data from
tb_vf_DAST_BUY_close to [vfdevelop2].[vf99uat2].
[tb_vf_DAST_BUY_close] Task"
..
..
..
Call oCustomTask2_Trans_Sub1(oCustomTask2)


goPackage.Tasks.Add oTask
Set oCustomTask2 = Nothing
Set oTask = Nothing
End sub

in the above Task I removed the 'Dim oLookup As
DTS.lookup" declaration statement. because I observed that
this variable is not doing any thing anywhere in DTS VB
program. does it cause any thing in the DTS Vb program?
And also in VB References i added Reference for Microsoft
DTSDataPump Scripting Object Library, Microsoft DTSPackage
Object Library. But I didnot add the reference
for "Microsoft DTS Custom Tasks Object Library". because
the program is running fine without this Reference, I
didnot add this reference. will it be a reason for not
copying some tables in DTS transfer.

pls response me.
rgds,
hari.

The custom task library refers to the new tasks that were added in SQL2000
such as FTP, MSMQ, Dynamic Properties etc, if you are not using any of these
tasks then you are correct, you do not need a reference to this library. If
you did and you are using early bound COM (which you are to be) then you
would actually get a compile time error not a run time problem.

--
-Euan

Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.

This posting is provided "AS IS" with no warranties, and confers no rights.

"hari" <hari_krishna_v (AT) yahoo (DOT) com> wrote