![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I've been poking around this newsgroup enough to come to the conclusion that Microsoft didn't design the DTS object model to be friendly to VBScript. This perplexes me, and I'm wondering if anyone can explain why? It seems like such an obvious candidate for a scriptable interface. And I haven't run into this kind of problem with other COM models for SQL Server (ADO, DMO, etc.). What were they thinking? Or were they just lazy? The case in point at the moment is the type mismatch problem with GetExecutionErrorInfo, which Darren Green has posted about many times. GetExecutionErrorInfo takes a ByRef Long parameter, and VBScript can't do that. I know there are workarounds for this, but they're painful (i.e. they all require a compiled language.) Can anyone offer any insight into this issue? And is there any chance we might see an update to DTS to address this? (I'm not going to hold my breath... they've already extended the interfaces to xxxx2 in many cases, which seems to be the end of the line most of the time.) Or am I using the wrong tool? The task I'm trying to accomplish is to import data from an Access .mdb file into SQL Server. Is there something else I should use to accomplish this from script? I exported a DTS job to Visual Basic, and I'm trying to translate that into VBScript. Thanks, Allan |
![]() |
| Thread Tools | |
| Display Modes | |
| |