![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Using enterprise manager to create a database export, save the task to vb file (dts.bas) I open up the dts.bas in VB and add the nec. references - the project won't compile until I correct some of the SQL statements, the when I compile and execute - in the weeds. The program reaches the execute statement then hangs, for hours. Is this a known issue? If so, then how is everyone using DTS? Robert |
#3
| |||
| |||
|
#4
| |||
| |||
|
| Some very long SQL statements are generated twice, once incomplete (this is commented out), the next one is generated incorrectly, it's really long and the generator screws up. I get - oCustomTask2.SourceSQLStatement = "select [a],[b],[c],[d"oCustomTask2.SourceSQLStatement = oCustomTask2.SourceSQLStatement & "],[e] from [DB].[dbo].[table]" where it is supposed to be - oCustomTask2.SourceSQLStatement = "select [a],[b],[c],[d]" oCustomTask2.SourceSQLStatement = oCustomTask2.SourceSQLStatement & ",[e] from [DB].[dbo].[table]" Not a problem for me to correct (incidently, this does not occur when creating the same DTS package that exports the data to XLS format - interesting.....). When I create the VB project and make the corrections (adding the sa password), I get no errors, no runtime errors, no errors in the event log, the program just hangs at goPackage.Execute That's it and thanks for you help. Robert *** Sent via Developersdex http://www.developersdex.com *** Don't just participate in USENET...get rewarded for it! |
#5
| |||
| |||
|
|
Interesting. I know that there was/is a problem with subs being too big and wouldn't compile. We had to break them dow into smaller ones. I have never seen yoour error but that could be that I haven't met your conditions either. What do you save out to VB and back again for ? Interested that's all. -- ---------------------------- Allan Mitchell (Microsoft SQL Server MVP) MCSE,MCDBA www.SQLDTS.com I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Robert Lassiter" <robert (AT) smartentry (DOT) com> wrote in message news:eo$QE68ZDHA.2580 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Some very long SQL statements are generated twice, once incomplete (this is commented out), the next one is generated incorrectly, it's really long and the generator screws up. I get - oCustomTask2.SourceSQLStatement = "select [a],[b],[c],[d"oCustomTask2.SourceSQLStatement = oCustomTask2.SourceSQLStatement & "],[e] from [DB].[dbo].[table]" where it is supposed to be - oCustomTask2.SourceSQLStatement = "select [a],[b],[c],[d]" oCustomTask2.SourceSQLStatement = oCustomTask2.SourceSQLStatement & ",[e] from [DB].[dbo].[table]" Not a problem for me to correct (incidently, this does not occur when creating the same DTS package that exports the data to XLS format - interesting.....). When I create the VB project and make the corrections (adding the sa password), I get no errors, no runtime errors, no errors in the event log, the program just hangs at goPackage.Execute That's it and thanks for you help. Robert *** Sent via Developersdex http://www.developersdex.com *** Don't just participate in USENET...get rewarded for it! |
![]() |
| Thread Tools | |
| Display Modes | |
| |