I am using the Bulk Export task with an ActiveX script. The script was
working fine a couple of days ago, but for some reason has stopped
working now. I am trying to dynamically set the ObjectName and the
ExportFile properties in the ActiveX script, but the script fails when
setting the ObjectName. The only error given is Unspecified Error.

I've tried debugging the script in VS.NET, but am unable to find any
more details on the problem there.

The portion of the script that is causing problems is shown below, and
it is failing on the line:

bulkExport.Properties("ObjectName").value = sTableName
TIA for any assistance.

Function Main()
Dim tableArray
dim bulkExport
dim sTableName
dim stpEnterLoop
dim stpFinished
dim pkg

set pkg = DTSGlobalVariables.Parent
set stpEnterLoop = pkg.Steps("DTSStep_DTSBulkExport.ExportData_1")
set stpFinished = pkg.Steps("DTSStep_DTSActiveScriptTask_2")

if DTSGlobalVariables("gvTableCount").Value <
DTSGlobalVariables("gvTotalTables").Value Then

stpEnterLoop.DisableStep = False
stpFinished.DisableStep = True
tableArray = DTSGlobalVariables("gvTableNames").Value

sTableName = trim(tableArray(DTSGlobalVariables("gvTableCount") .Value))

set bulkExport = pkg.Tasks("DTSTask_DTSBulkExport.ExportData_1").Cu stomTask
bulkExport.Properties("ObjectName").value = sTableName
bulkExport.Properties("ExportFile").value =
DTSGlobalVariables("gvExportDirectory").Value & sTableName & ".txt"

DTSGlobalVariables("gvTableCount").Value =
DTSGlobalVariables("gvTableCount").Value + 1

First check that your ActiveX Script Task is Execute on main thread, under
workflow properties for that task.
Assuming that is set then I can only assume it is the value itself that you
are trying to set that is causing problems.

You could try logging the variable value or just throwing it count via
MsgBox. You could also try using CStr to try and force and bad data into a
string. This might highlight the problem.

bulkExport.Properties("ObjectName").value = CStr(sTableName)

Not the problem here I suspect, but I always use Option Explicit as well as
this often catches silly mistakes in script.

Darren Green
http://www.sqldts.com

"Allister Farn" <a_farnsworthy (AT) yahoo (DOT) com.au> wrote