DSXchange

Oh, they all can be installed...

Yes.

As noted, it is not the correct version to run PX jobs on Windows. They can be developed, sure, but not run.

Not really all that strange and the message tells you the problem. The only pre-8 version that runs PX jobs on Windows is 7.5x2. Yes, with an 'x'.

No. 7.5x2 (note the 'x') is the only pre-8 version that will run PX jobs on Windows. And no version officially supports XP as a server platform.

Why not include the 'reject message' on the aborting link? What do you ultimately need to do with this? The presence of a non-zero byte file could trigger an email with the file as an attachment, something easier than fishing the error out of the job logs.

Just a thought.

As noted above, use constraints to control what goes down the 'good' link and what goes down the 'bad' link.

Can you not use the old trick of supplying your own EOR characters in a string to create multiple records from a 'single' record? There's a FAQ on the subject, btw. Use the logic noted in a transformer to still produce 'one' record, but one that will (at the appropriate times) turn into two when lan...

From what I recall, you could also use OConv to automatically 'adjust' a date that has overflowed a month, if that works for your requirements. For example, adding six months to 08/31/2007 gives you 2/31/2008. If turning that into 3/2/2008 is the answer rather than 'rewinding' back to 2/29, that can...

Kudos! :D

You would have had to have imported the metadata for the View and used it in your jobs. Then a Usage Analysis on it would show you all of the jobs that you've used it in.

Use the Field function, which extracts 'fields' from inside a delimited string. For example, Field(LinkName.FieldName,';',4,1) on this record:

Inventory;000202;13TCM;UR_TCM_F;0022008 00:00;

Results in "UR_TCM_F".

Actually there is a command, I'd not heard of it until someone else mentioned it here some time ago. And I tend to forget about it because of the name - iconv. iconv -f fromcode -t tocode [file ...] iconv converts the encoding of characters in the input file from the fromcode code set to the tocode ...

Perhaps if you posted both the constraint and the compiler error it generates?

What settings are you asking about? There are no database settings for commits.