DSXchange

Must be. The column names don't need to match but all columns promote "positionally" so the input column type must be convertible to the output column type.

You didn't "delete the project", all you've managed to do is corrupt it.Always always always delete from the GUI not from "under the covers". Here, that would mean the Delete button when logged in as the admin to the Adminstrator client.

When writing, 'string' columns are automatically quoted while 'numeric' fields are not. Why not simply try it and see if it works the way you need?

Yes, doing it right after the fact can be a little painful but would mean the problem would be solved forever, immune to any issues you are struggling with right now. Sure, that TO_CHAR() would force the results to be the same in both environments. You need to determine what is different between the...

Old dog? Meet new trick.

Need to file this one away for future reference.

Nit pick alert!

You do not need to specifically set an expression to "true" or "false", that is automatic when it is evaluated. So rather than the derivation posted for svInd, it can simply be:
FYI.

Project parameters are environment variables, set in all jobs when they run. Double-click on the second log record from any job to see what I mean. Unless we have a different definition of "project parameter" that is.

You want to read a report, eh? You'll need to read it as one long varchar field, skipping and parsing it appropriately based on what you find in the first few characters of each record.

For example:

Field(Link.N_NAME_SEEK,",",1,1) = First Name
Field(Link.N_NAME_SEEK,",",2,1) = Last Name
Field(Link.N_NAME_SEEK,",",3,1) = Title

Sure, it can handle it pretty much as noted already unless you have no idea what the maximum number of delimited values in the second column might be. Otherwise, pick a max, split out the values to separate columns, pivot then filter out the null values.

There are separately licensed (and purchased) versions for Windows and every flavor of UNIX. And no, you cannot install Windows software on a UNIX machine.

What format do you actually want in the sequential file? If you want the YYYY-MM-DD format shown in your SQL, the data type would either need to be Varchar or Timestamp. The former you could use directly since there are no other data types in a sequential file while the latter would require removing...

You might also consider reading the documentation on the stage. Crazy thought, I know, but it may actually help answer some of your questions.

I'm curious how reading anything would corrupt it? :? Is there any thing similar to PX's GetEnvironment for the Server Edition or is there any other way to get it. Roll your own. It would be simple enought to "echo" whatever variable was passed in and return the value associated with it.

In that case, using IConv only doesn't make much sense, but I'll take your word for it that it is actually working for you.