accessing components and task from scripting task

Hi, I have to researching of how to accesss package tasks and component using the SqlServer.Dts.Runtime class and so far, I havent found any solution. For example, if you package has a scriptiong task and a data flow task(<- which contains a data source component). Is it possible to use the scripting component to access the data source component in the data flow task and manipulate its properites like sqlcommand etc.

Emmanuel

An easier and more direct way to do this is to store the sqlcommand for the datasource in a package variable and set the variable value in the script task or even at the time of executing the package.

|||I know that can be done using variables and expressions and all that but i want to know where its possible to access component and dask of a package in a scripting task using a SqlServer.Runtime library. I know you can pass variable around be I want to know how to control component properties in a scripting task or component if possible. If anyone know how to do that or can direct me to the right resource, I will be glad. Thanks.|||Nope, the tasks and components can't directly access each other at runtime.

Access Violation on Saving a DTS Package

Hi MS Newsgroup

I am using SQL 2000 SP3 + latest hot fixes and I am editing a DTS
package. When I save the package I get a SQL Server Access Violation
and cannot save the package. This does not crash SQL nor Enterprise
Manager but no matter what I do I cannot save the package. This occurs
for only 1 package on the server (others are ok) and for all users of
any privilaged access level. I have tried to save to file, VB, etc but
all fail similarly.

I have read MS KB and have tried all options they suggest but to no
avail! I'd like not to have to rewrite the DTS again from scratch.

Ideas anyone?

Thanks"Rolf" <tesmerr@.hotmail.com> wrote in message
news:c85859d1.0504182046.2e231566@.posting.google.c om...
> Hi MS Newsgroup
> I am using SQL 2000 SP3 + latest hot fixes and I am editing a DTS
> package. When I save the package I get a SQL Server Access Violation
> and cannot save the package. This does not crash SQL nor Enterprise
> Manager but no matter what I do I cannot save the package. This occurs
> for only 1 package on the server (others are ok) and for all users of
> any privilaged access level. I have tried to save to file, VB, etc but
> all fail similarly.
> I have read MS KB and have tried all options they suggest but to no
> avail! I'd like not to have to rewrite the DTS again from scratch.
> Ideas anyone?
> Thanks

No idea - reinstalling the client tools might be worth a go if all else
fails, which admittedly isn't a great answer. You might try posting in
microsoft.public.sqlserver.dts to see if anyone there has seen this before.

Simon

Access Front End?

Is there any way to set up a database, that was access but I transfered it into SQL 2000 using DTS, so that the front end of the database is using Access 2000 but the backend is SQL Server 2000? I want to do this, or something like it so that people can use the database to create queries and reports, but utilizing the SQL database.You can link the SQL Server through an ODBC data source within the Access db. You have to be careful though, that some SQL data types are not recognized/supported in Access. If I remember correctly, bigint is one of them I think.|||I did that and it will not allow me to add or delete records (using the access front end) in the tables that I have linked back to the SQL database. Any ideas why?|||Does the account you used to set up your ODBC connection have the necessary permissions to delete files in the database?

Do the tables in question have a primary key/unique identifier as this is required if connecting through an ADP or OLEDB connection.

Cheers,
Andrew|||Here's a "new" problem. I have this database set up so that it has an access front-end and an SQL backend. When I open the database on a computer with the SQL Server client installed it runs fine. When I open the database (access front-end) on a computer without the SQL client installed it prompts me to enter some login information to connect to the server. Is there any way to modify this front-end/backend so that the login information is automatically entered and it does not prompt the user to enter it?