dbTalk Databases Forums  

DTS VB Issue

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS VB Issue in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Robert E Lassiter
 
Posts: n/a

Default DTS VB Issue - 08-20-2003 , 04:37 PM






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



Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: DTS VB Issue - 08-21-2003 , 01:14 AM






What are the statements you corrected. There are things you can comment out
to decide if to execute it or save it back. What are the errors?

--

----------------------------
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 E Lassiter" <robert (AT) smartentry (DOT) com> wrote

Quote:
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





Reply With Quote
  #3  
Old   
Robert Lassiter
 
Posts: n/a

Default Re: DTS VB Issue - 08-21-2003 , 05:25 AM





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!

Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: DTS VB Issue - 08-21-2003 , 05:30 AM



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

Quote:

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!



Reply With Quote
  #5  
Old   
Robert E Lassiter
 
Posts: n/a

Default Re: DTS VB Issue - 08-21-2003 , 05:41 AM



Yes, very interesting, especially when the export to excel work OK using the
same sql statement.

My immediate goal is to write a VB service that exports a couple of tables
from the database and email them to an analysist. I guess I could do this
using ADO but I wanted to take advantage of the wheel already haven been
built.

Thanks
Robert


"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Quote:
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!





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.