![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Hi, i have created the dts package and saved as vb module. the package created for exporting access db values to sql server. and then i try to run the vb project. its execute complete code. but its not exporting the data. whats the problem? thanks bala |
#2
| |||
| |||
|
|
i have created the dts package and saved as vb module. the package created for exporting access db values to sql server. and then i try to run the vb project. its execute complete code. but its not exporting the data. whats the problem? |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
In article <B73C6C2E-EDF6-45CC-8776-DA32049FA83D (AT) microsoft (DOT) com>, Bala wrote: Hi, i have created the dts package and saved as vb module. the package created for exporting access db values to sql server. and then i try to run the vb project. its execute complete code. but its not exporting the data. whats the problem? thanks bala It is unclear whether you have commented out the line that saves it to SQL Server or the line that fires the package. Supposing you are actually executing the package then you can add another line to your code to make sure any errors are raised to VB and that line is pkg.FailOnError = TRUE Why are you firing the package like this? Effectively you are rebuilding the package every time which for me has to be a performance hit Allan Mitchell (Microsoft SQL Server MVP) MCSE,MCDBA www.SQLDTS.com www.konesans.com - for all your consultancy needs |
#5
| |||
| |||
|
|
Hi, when the user try to run the package once again i am getting error. how to resolve this error? -2147217900 DTS Package 'New Package' already exists with a different ID in this category. thanks bala "Allan Mitchell" wrote: In article <B73C6C2E-EDF6-45CC-8776-DA32049FA83D (AT) microsoft (DOT) com>, Bala wrote: Hi, i have created the dts package and saved as vb module. the package created for exporting access db values to sql server. and then i try to run the vb project. its execute complete code. but its not exporting the data. whats the problem? thanks bala It is unclear whether you have commented out the line that saves it to SQL Server or the line that fires the package. Supposing you are actually executing the package then you can add another line to your code to make sure any errors are raised to VB and that line is pkg.FailOnError = TRUE Why are you firing the package like this? Effectively you are rebuilding the package every time which for me has to be a performance hit Allan Mitchell (Microsoft SQL Server MVP) MCSE,MCDBA www.SQLDTS.com www.konesans.com - for all your consultancy needs |
![]() |
| Thread Tools | |
| Display Modes | |
| |