Check this out:

http://www.sqldts.com/234.aspx

create proc myproc

@MSBA_ID varchar(10),

@Phase_ID int = null,

 @GSF int,

@Note varchar(100)

if exists (Select 1 from [dbo].[COST_Project_Phase]

   where MSBA_ID = @MSBA_ID and Project_Phase_ID = @Phase_ID)

begin

insert into dbo.[COST_Project_Phase](

 [MSBA_ID],

 [Gross_Square_Footage] ,

 [Phase_Note])

values (@MSBA_ID, @GSF,...

The transaction log (in full recovery mode, the default) records all of the changes to data.  Products such as Lumigent log explorer will help you to read the log.  There are...

My guess is that your problem is with the networking.  When you run a DTS package from a client machine all of the data is pulled to that client machine...

See if this will help:

http://www.sqldts.com/225.aspx

That shouldn't be too hard.

You need one SQL Server connection and two tasks:  a dynamic properties task and an executesql task.  Link the two with a workflow.

In the dynamic properties task, assign...

You could recast this as a group by query, with every field (except for ID) in the group by clause.  You could then choose to get the Max(ID), Last(ID) (Access...

select lref . empname, total.total1

from emp inner join total

on emp.EmpNum = total.EmpNum

inner join Labor_Dept

on Labor_Dept.Lentry = total.lent1

where emp.lent2 <> total.lent1

I think that your best bet is to use the linked table manager.  Change the DSN in the ODBC administrator tool to point to the server and database.  Then go...

Can you give a sample of the data from each of the tables as well as a short narrative of what you want to see in output and what each...

Are you using an Access mdb?  Does each person have their own Access mdb?  Do you know how to use the immediate window?

First correct this section of code:

oStep.DisableStep = False

 oStep.ExecutionStatus = DTSStepExecStat_Waiting

 oStep.DisableStep = TRUE

Next, add an ActiveX task.  That task will have these lines of code:

dim oStep 

Set oStep = oPkg.Steps("DTSStep_DTSExecuteSQLTask_4")

 oStep.DisableStep = TRUE

Next,...

I found that this code returns an error if run in the designer.  You could put:

on error resume next ' This will cause errors to not fire.

I've never used the print statement and I couldn't get it to work.

Try this:

dim fso

dim txt

set fso = CreateObject("Scripting.FileSystemObject")

set txt = fso.GetStandardStream(1) ' Get the stdout

txt.WriteLine SelectStmt

Why do you need to disable it?  Once the task runs once, it will not start running again, until you run:

oStep.ExecutionStatus = DTSStepExecStat_Waiting

Once it runs, it acts like it has...