DSXchange

BYTE is the default, btw.

I think you are right about the 'finding it' part. I went back through an old job that uses that feature and while it is an XML Output stage rather than an input, the annotation says it needs to be in the same directory as the xml for the 'relative' path in the schemaLocation to find it.

The Server edition does not require a C++ compiler be installed, that is only a requirement for the Enterprise / Parallel Extender edition.

Please do not start a new thread just because the original hasn't come to a conclusion yet. All you are going to do is attract people who aren't aware of your ongoing saga and you'll start getting the same advice all over again. If people want to help, do so in the original thread please: m

Exactly, it would need to be in the Project folder (and moved with the job) for that relative path to work. As noted, not a Best Practice.

You should provide a full pathname to the xsd. And it should be "schemaLocation" as far as I know, the case matters as well.

You have a date or a string in date format? What do you plan on using for the time portion - zeroes?

This is well worth repeating:

lstsaur wrote:Read the stpstage.pdf file under the Doc folder.

No, it does not support "sub-folders".

CHAR(9)

Depending on your definition of 'subject group'... I prefer to keep them in separate projects.

Yes, that's the 'why' that I am aware of. That and you have no clue if there were warnings under the abort limit without looking in the Director log.

Ok, see that now. As noted, that's what happens when you move away from a 'one line' statement.

Confusing. I don't see any evidence that you are attempting 'multiple statements' in an if. Can you clarify? And your problem is - won't compile? Doesn't work as expected?