DSXchange

An exact search for "because of a prior component with the same name" got me 27 hits including your post, did none of them help?

I believe you'll find that DSGuru2B posted a PX version of EReplace here some time back. If memory serves.

I would suggest trying "Import selected" so you can confirm that you do indeed only have one thing (the right thing) in your export file as it will show you the contents before importing.

Search the forums for "vertical pivot", it has already been discussed here. Alot.

Exactly, add a null column to the first query so you can do a UNION ALL with the data. You're going to need consistent metadata in the output file for it to be read properly. That or concatenate the data fields together into one comma delimited string for the union, then you could easily write out w...

That just sounds like a SQL join between those two tables, pulling all columns from each. Is there more to it than that? If so, can you provide input & output examples?

"By single element" means you created a dsx file with *just* one custom routine in it and you still could not import it?

Just include your routines in the dsx file and leave the read only objects excluded. If they are in a unique folder that should be easy, worst case export individually and append.

Like most everything in PX, there is a specific stage for that function: the Surrogate Key Stage.

Are your "custom BASIC routines" read-only? There really shouldn't be any need to include read only items unless they are, that option is meant to exclude all of the built-in routines that ship with the product.

What database? What have you tried and what problems are you experiencing?

I modified a version of Chuck's utility to write the output to a database table so I can query the results. Work'em good.

No, or at least not yet. That you need to script.

Search the forums for dsdesign.exe which can be scripted to do what you need. Or grab an existing script from Kim Duke's website from his Tips & Tricks section.

The online help for the Sequence job option 'Automatically handle' fully explains how to handle that situation.