An alternative is to keep the Access database simply as your application front-end and use linked tables to point to the new SQL Server tables (that you imported from this...

Are the packages scheduled to execute as a job?  Does the SQL Agent have access to the directories that contain the INI files?  Are you using UNC paths?

Try going through the Import/Export Wizard and save the DTS package at the end and then try going into the TDT.  Does it crash when EM creates the DTS package?

Have you tested other connections besides DB2?  Does this crash behavior happen with an Access connection? 

Not sure about your configuration, but you may need to use UNC convention  (\\server\path\file.ext)

In an ActiveX Script, add the following code.

Add this task just before the connection object.

Function Main()

Dim oConn

Set oConn = DTSGlobalVariables.Parent.Connections("your_Connection_Name")

oConn.DataSource = DTSGlobalVariables("your_MDB_Name").Value

Set oConn = Nothing

Main = DTSTaskExecResult_Success

End Function

Try:  sp_helprotect

When you say "during the installation of the package", what do you mean?

Can you write the connection information to a table during installation after prompting, then refer back to this...

See similar post at...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=6&messageid=137244#bm137406

Should be able to use for both source and password.

The following script looks up the password from a table using ADO and then updates the connection.  Simply add this as the first task of a DTS package and whenever...

You can accomplish this task in two ways.

1)  Create the same text file every time and use FSO to rename the file to include the date/time in the name.

2)  Dynamically...

As mentioned above, this is an encrypted string, normally created by right-clicking on a DTS package and selecting 'Schedule'.  If this is the method used to schedule the job, then...

I've noticed something similar in WinXP -- it will let you go through the steps of creating a DSN in the ODBC Administrator, but unless you have admin rights, it...

As suggested above, take a look at the error message from the job history -- better yet, turn on logging in the job for a better, more meaningful message.  In...

Another idea is to put the query in a stored proc and then call the stored proc from a pass-through query from within Access.