Errr... even if I put the sproc calls as the code in each dataset, how do I guarantee that the second stored procedure will indeed execute second??  The query/call in...

That's exactly it. I can execute them in the exact order I need. It's cool, really, you can almost treat it like you would SQL Server. Perhaps...

Not a bad idea, but the problem is that I need the second dataset to pull data from the table after the first dataset truncates the table and repopulates it. ...

Don't think that would work.  I'm populating a whole table in the first dataset (among other things) and then selecting from that table for the second dataset.

Yeah, I've done the pass-through thing with ADO and am aware of CommandTimeout and ConnectionTimeout.

I'm really quite irked that my problem was something as simple as a Property of the...

Of course!  If not for people doing the same, I'd never have found half the solutions I needed. 

Yes, thank you, noeld, I did read the link you posted. 

Zero is less than 60 but I figured since zero is supposed to...

From what I've read, setting it to 0 means it will never timeout, but regardless, I've tried setting it to 600, 6000, etc.  But it seems to be ignoring it...

Please post to this thread:  http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=131&messageid=203232.

Thanks, Dave (do you mind if I call you Dave?  )

I found a 16kb executable that allows for copying a file beginning at a...

That works great skipping the header row, but it also skips row 2 (the first data row).  The import then starts on row 3. 

Also, is there any method you guys know of to strip just the header row from a text file?  If I could do that (from an xp_cmdshell from within SQL...

Thank you.  Although I am checking for file existence after both download and decompression, I'm not doing it the way they do in the article's function.

I'm still skeptical that this...

That's not a bad idea, but it doesn't feel right.  These files are indeed quite large, but after being downloaded and decompressed, SQL Server goes to drop the indexes on...

Argh.  It stopped again right after the one second delay but before beginning the insert transaction.  This doesn't make any sense!