Hi,

Maybe a silly question, but here goes

I'd like to create dts packages that do (whatever...something generic and
dynamic)
and package them with other software (c / vb6 exes) to distribute (maybe
using installer scripts such as Wise or InstallShield)

I know end users will already have SQL Server 7 or 2000 on their system.

I won't know user names / passwords and the like in SQL Server

Can I:
a) automate the dts package installation on the destination machine?
b) lock end users out of viewing / editing the package yet still run it
from other software calls?
c) and if possible, is it legal to sell custom dts packages?

thanks in advance

georgejetson

A) Yes. Look at the SaveTo* methods on the Package object
B) Password protect the packages. Distrib only the user password not
the owner password.
C) A custom package? Custom Tasks yes but I am not really sure about a
package. The end user would need at least the client libraries (unless
you install them) would need licencing (perhaps if you connect to SQL
Server).

Allan


"georgejetson" <georgejetson (AT) discussions (DOT) microsoft.com> wrote