DSXchange

Count the number of separators and then dynamically use that to extract the 'last' FIELD. I've done this many times with a single separator character, having '\\' as one should be possible. At worst case, count the number of them and divide by 2.

DSguru2B wrote:Using the Clear.File option would it be the same as deleting the file.

Umm.. no. Do the CLEAR.FILE and then re-establish the auto-purge settings.

IMHO, you've listed them from least to most desirable.

'Some one' needs to be punished.

If you reset the job after it aborts, is there an entry in the log labelled 'From previous run...'?

There were some significant changes in that stage between 7.5 and 7.5.1A from what I recall. Perhaps you should take one of the offending jobs, remove the stage from it and rebuild it with the 7.5 version of the stage. Perhaps that will help. Always a little dangerous to go 'backwards' in versions.

Interesting... 'they' specifically state in the readme that they will no longer log this. I'd suggest two things: report it to your support provider and search the forum as it has been discussed many times. I believe that Ray even posted the cause, but don't recall off the top of my head.

Yes sir. That would be correct, sir.

Yes, sorry... forgot not all peoples live on Planet Ellison.

You mean 'append' mode. Search for the SEEK command.

That's odd as that is the situation where it is supposed to matter where the reject row link is in the output link order.

The answer will depend on if just the Reject Row check box is checked, there is an expression in the Constraint derivation - or both.

If you have version 7.5.x then - Sequence job: Start Loop, End Loop and UserVariables Activity stages will get you what you need.

Search, my pastey friend, search!

See if either this post or this post helps.

Have you tried just reinstalling the client?