DSXchange

Specific? No, don't believe so. Does it support ODBC access?

No.

Well... unless you count writing a BuildOp or some other external solution as a 'single stage' solution.

You need the column headers. The suggestion is to read them in as data, note which one is which and direct the output for the rest of the lines accordingly.

So why not use the Enterprise stage? Did you try it and have issues?

I certainly haven't. The Sequential File stage is a 'blocking' stage so it finishes all of the writes before it open the file on the reading side. I've done exactly that many times in the past without issue.

FWIW, that 13 means "Invalid data".

ray.wurlod wrote:Yes, but not if you insist upon using command line utilities.

I'm not aware of anything in the API that does not have a command line equivalent, so it should just be a choice between BASIC coding and shell scripting. Yes?

True. My 'one time' was back when that was the only option. Ah, those were that days.

If you are supplying 'user-defined' SQL it seems to me you'll need to correctly supply / specify the parameters as well. That helper isn't going to know where to put them, unless you help it. Just guessing but have you tried highlighting where the parameter should go (what it should replace) before ...

Where are the hash signs around the parameter names?

Transformer with looping would be your 'single stage'.

The one time I did XML validation, the xsd had to be in the Project directory otherwise no workie. But that was a long time ago so I wasn't sure if that had changed.

Hard to say with so little information. What purpose does this column serve?

Not much to guide. Declare it as the trigger column, send in the value and each time it changes a new file will be opened / started. Of course, this means your data really should be sorted on that field at the very least.

Sorry, I can't but for any kind of "unknown reason" failures I be involving my official support provider.

From what I recall, it's looking for it on disk. And a relative path like that would mean 'in the current project'.