As I stated in line 1 of my message, I'm using a script component (in the
Data Flow section) not a script task in the Work Flow section, therefore I'm
unable to set breakpoints and determine which line causes the exception.

However, I can try other methods talked about in MSDN article "Coding and
Debugging the Script Component"
(http://msdn2.microsoft.com/en-us/library/ms136033.aspx) to determine the
suspect code.

I guess I was hoping for some help from Microsoft, I'm kind of stuck here.





--
Dave B.


"Charles Wang[MSFT]" wrote:

> Hi,
> I understand that when you executed your script component, you encountered
> the error of "object reference not set to an instance".
> If I have misunderstood, please let me know.
>
> This issue seems to be closely related to VB.NET programming. Anyway I
> recommend you first debug your script to first identify which line threw
> this exception and then let us know the place for further research. You can
> refer to the following articles for debugging script:
> Debugging Script
> http://msdn2.microsoft.com/en-us/library/ms142157.aspx
> How to: Set a Breakpoint in Script in a Script Task
> http://msdn2.microsoft.com/en-us/library/ms140033.aspx
>
> If you have any other questions or concerns, please feel free to let me
> know.
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>
>
>
>
>