DSXchange

As already noted, it's all about the number of columns defined in the stage versus selected in your DML and what you've marked as keys. For yours to work, there must be three columns defined in the stage (in the order mentioned in the sql, of course) with none of them marked as a Key. Key fields mus...

Ah... and here I thought there actually was such a thing. Never mind.

(next thing you know you'll be telling me there's no Tooth Fairy or Sasquatch... sheesh)

Pre-load file to memory enabled or disabled, with the added bonus of the record being 'looked up' locked during the process... and the manual seems pretty detailed on how it works to me: Pre-load file to memory. You can use these options to improve performance if the output link is a reference inpu...

Timestamps have no external format, the mask in the function must match what is coming in in the string field, not what you think it should look like.

No actual experience, but I would wager you would need to build a QualityStage job rather than a Parallel job for those stages to be active.

It may be moot but can you post the full log entry from executing this from (I assume) a Routine Activity stage? And just for grins, what exact O/S and Service Pack are you running?

Sure, an Enterprise Scheduler would handle something like this quite easily.

You could use dsjob rather than polling for a flag in a table to run the job in the other project but it's still a form of "coding in" something.

When I said "ExecSH" I actually meant "DSExecute". D'oh.

Try it and let us know. It's not "officially" supported as a server platform but that doesn't necessarily mean it won't work.

Interesting, me running an "FC" manually from the command line does indeed output to the screen and I don't see a way to suppress that. I created two identical files and got this: C:\Temp>fc /b fred1 fred2 Comparing files fred1 and FRED2 FC: no differences encountered When I then created a...

That's not an error, it is just letting you know that the command sent nothing to 'the screen' i.e. standard out. Your 'result' should still be being passed back correctly.

Then your next stop should be your official support provider.

You should add $APT_DISABLE_COMBINATION and set it to True before running the job again. The error will 'persist' but will tell you where (what stage) it is actually coming from, which can help with the diagnosis. Do that and repost the error. ps. No reason to be 'stuck for two days', hopefully you'...

Have you tried escaping the inner quotes?