Thank you all for the time you guys have given to help me out! Much appreciated.

The users also need to see what data was there in the file and what was matched through a web application and then reports are run off of that data...

Elliott Whitlow (12/13/2011)

---

Elliott Whitlow (12/13/2011)

---

I apologize, in the absence of gender specific identifiers I assume "he". This time I was mistaken.

I would like to understand the process more, because...

Elliott Whitlow (12/13/2011)

---

I apologize, in the absence of gender specific identifiers I assume "he". This time I was mistaken.

I would like to understand the process more, because it seems...

Elliott Whitlow (12/13/2011)

---

I apologize, in the absence of gender specific identifiers I assume "he". This time I was mistaken.

I would like to understand the process more, because it seems...

--and this is a "SHE" 😉

Elliott Whitlow (12/13/2011)

---

You may not add an output after the OLEDB destination. It is the end of the pipeline for successful records.

However, may I ask a dumb question. ...

This gives you last day of the current month

SELECT convert(varchar,DATEADD(s,-1,DATEADD(mm, DATEDIFF(m,0,GETDATE())+1,0)),101)

I tried something like this but now reaching a road block

Declare @stopTime as varchar(7),@SystemNowTime as varchar(7),@EOMdate varchar(10)

SET @EOMdate = convert(varchar,DATEADD(s,-1,DATEADD(mm, DATEDIFF(m,0,GETDATE())+1,0)),101)

SET @stopTime = '11:30PM'

SET @SystemNowTime = RIGHT('0' +...

GSquared (12/2/2011)

---

Guras (12/2/2011)

---

GSquared (12/2/2011)

---

Guras (12/1/2011)

---

GSquared (12/1/2011)

---

Of course, the other option would be to put a first step in those jobs that would check the time/date, and cause the job to...

GSquared (12/2/2011)

---

Guras (12/1/2011)

---

GSquared (12/1/2011)

---

Of course, the other option would be to put a first step in those jobs that would check the time/date, and cause the job to abort if...

GSquared (12/1/2011)

---

Of course, the other option would be to put a first step in those jobs that would check the time/date, and cause the job to abort if run during...

I did something like this

Declare @errMsg varchar(1000)

If @enableFlag = 0 --disable jobs

BEGIN

BEGIN TRY

exec msdb..sp_update_job @job_name = 'Update_job1', @enabled = 0

END TRY

BEGIN CATCH

...

I took the route of what HowardW sugested since I realized there were some notifications jobs that needed to be running.

Here is my sp

CREATE PROCEDURE [dbo].[PROC_SQLJOBS_ENABLE_DISABLE] (@enableFlag...

no, the application is a vb.net Winform apps