DSXchange

Right click on the open expression window in the user variable activity for the variable you defined. Choose the option of 'Activity Variable'. You will have three options listed. Choose '$CommandOutput'

Did you take a look at the after job subroutine "DSSendMail". You can send an attachment with that routine.

How about this?

What i meant was to code the Job Control as Ray indicated and put a loop in it. Search this forum for sample Job Control's. A sequence is basically a Job Control. The only difference is that its all GUI. When you build a sequence, the DSEngine builds the Job Control in the back end. If you are comfo...

Datatype and data length issues.

Click here to go to the post that vincent is talking about. If you can partition your data on the group (AccountNo+BillNo) then you can get a counter set up by using two stage variables. Read that post, it will get your work done.

In your sql select, try to change the timestamp to char in your sql and see if your query executes. SOmething like

DSJobStartTimestamp will be the same for all the records in a particular job. Current Date and Current Time from DATE() and TIME() will be the same for the first several records. The remaining two can be same as you said. There you go. You have identical combinations of your keys, or composite key. ...

Funny ....

Yes i will do that. After a few thousand more posts
Really, still a long way to go.
Barely got my feet wet in the sea of DS knowledge.
Thanks though, gives a great boost to my confidence.

Meaning less huh....can I get some?

where LAST_ UPDATED > (select MAX(LAST_UPDATED) from table_name where <condition for yesterdays rows>) Once again. Something like that will always retrieve 0. It should be ...where LAST_UPDATED > #LastRunMaxTimeStamp# or if your storing the Max timestamp of previous run in some other table then the...

Ok, i posted on the other thread without going through this one first. Same suggestion as getting your DBA involved. Do come back and let us know what was the core of this chase.

Go to your DBA. Get him/her involved. It doesnt make sense that even after dropping all the primary keys your getting this error. See what he/she has to say.

What type of database are you dealing with? What is the length of timestamp there? If it supports milliseconds, then i would say keep your milliseconds in tact if your going for a string comparison.
In the end, 2000-09-07 09:26:27.000 is different than
2000-09-07 09:26:27.003