"Nex" <nex@nex.com> wrote in message news:2jgvktF10lk8uU1@uni-berlin.de...
> Hey all,
>
> A simple statement below:
>
> DROP TABLE [Table_1]
>
> What I'm trying to do--essentially--is this:
>
> DROP TABLE [?]
>
> And pass in a global variable as a parameter. Conventional
> wisdom says that with DROP's and CREATE's it's not
> possible to do this. I say to hell with conventional wisdom,
> I'm sure someone out there has done this before. FWIW,
> I did see a reference to a "gvcustomtask" on sqldts.com which
> would allow for such things, BUT, it involves outside code
> with a "use at your own risk" disclaimer, so I'm somewhat
> leery of bringing it into a production environment.
>
> Ideas, anyone? Thanks very much!

"Nex" <nex@nex.com> wrote in message news:2jh1rfF11b26iU1@uni-berlin.de...
> Never mind, I ran it in as an "execute sql task" but ran the sql through
> the workflow properties as an activex script. Got the variables in that
> way. Works like a dream.
>
>
> "Nex" <nex@nex.com> wrote in message news:2jgvktF10lk8uU1@uni-berlin.de...
> > Hey all,
> >
> > A simple statement below:
> >
> > DROP TABLE [Table_1]
> >
> > What I'm trying to do--essentially--is this:
> >
> > DROP TABLE [?]
> >
> > And pass in a global variable as a parameter. Conventional
> > wisdom says that with DROP's and CREATE's it's not
> > possible to do this. I say to hell with conventional wisdom,
> > I'm sure someone out there has done this before. FWIW,
> > I did see a reference to a "gvcustomtask" on sqldts.com which
> > would allow for such things, BUT, it involves outside code
> > with a "use at your own risk" disclaimer, so I'm somewhat
> > leery of bringing it into a production environment.
> >
> > Ideas, anyone? Thanks very much!
>
>