hi again )

everytime after I store my dts-package via vb with Package.SaveToSQLServer
the presentation of the package in SQL Server 2000 has changed. the whole
arrangement of tasks & constraints has changed and the text-box has
vanished...
now it is very unstructured and very hard to follow.

is there method or a flag, that i can set, that helps to keep the package
assembled as it was before I gained access (via vb) to it?????

thanks in advance hendrik

This is a known issue, and there is no magic flag to help you out. It is the
price you have to pay for manipulating a package in this way.


--
Darren Green
http://www.sqldts.com

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

Somehow, I have foreseen this answer (

nonetheless, thank you again

do you have any idea how the dts designer saves the packages without loosing
the logic arrangement ???

greetings hendrik



"Darren Green" wrote:

The "designer" produces a separate data stream for layout which is saved
alongside the object model stuff.

Unfortunately there is no way to capture this designer stream. Even if the
was, changing a package would then break it as the layout no longer matches
the object model, so total mess. You can do similar sometimes by using code
inside the designer, and it breaks your package basically, when the two get
out of sync.


--
Darren Green
http://www.sqldts.com


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