Hi !

Well, im having my first steps with MSSQL and I have a
small problem. I've created a package that retrieves data
from an AS400 system and specifically from a multimember
file. I need to create each time a date format
like '200407' and pass it in an SQL Execute Task as
parameter. I've created a string variable and Im trying to
assign the value from MSSQL Execute Task and pass it to
the AS400 Execute Task using the SELECT INTO :test etc.
How do I pass the params to the task execution ?

Thanks and appologies for the newbie question

Enigma

Global variable parameter support fro SQL tasks did not arrive until SQL
2000, so for SQL 7.0 you will need to manipulative SQL string directly in a
script task.
Global Variables and SQL statements in DTS
(http://www.sqldts.com/default.aspx?205)


--
Darren Green
http://www.sqldts.com
"Enigma" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Ive tried to create it on an SQL 2000 as well. I have my
param named tmpmember and Im trying to place it on the
AS400 Execute task. It doesnt seems to work

It goes like this

CREATE ALIAS LIB1.TEST FOR LIB1.FILE1(@tmpmember)

What Im doing wrong ? The Global Variable has the correct
value

Thanks

In article <2e03601c46b11$8d20ce50$a401280a (AT) phx (DOT) gbl>, wrote:
You may want to try

CREATE ALIAS LIB1.TEST FOR LIB1.FILE1(?)

But that still may not work depending on the driver so an answer would
be to use a variation of this method

Global Variables and SQL statements in DTS
(http://www.sqldts.com/Default.aspx?205)


Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs

Appoligies for my newbie questions but how am I going to
implement this

In article <2e30801c46b17$1795ce50$a501280a (AT) phx (DOT) gbl>, wrote:
The first one.

You type in the command I gave you to the ExecuteSQL task. You will
see (SQL Server 2000 only) the parameters button. If upon pressing
that you get an error then the chances are the driver does not support
this OR the design time interface to this task is not playing ball. If
on the other hand you do not get an error you should be able to map on
the Input Global Variables Tab a Global Variable declared in your
package. This will be resolved at runtime

The second one.

This option is available in 2000 and 7. You add an ActiveX Script task
before the executeSQL task and join it to the ExecuteSQL task through a
workflow constraint.

Introduction to Workflow
(http://www.sqldts.com/default.aspx?287)

You substitute the name of your ExecuteSQL task for the name that we
provide in this article.




Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs