DSXchange

Suman wrote:Is there any reason for failure.

Of course there is, but *you* would need to tell *us* the reason. Post the actual errors that you get when the 'Load' option is used.

Indeed.

'non-printable' characters, eh? So they're not actually spaces, it would seem. What does a quick peek with a hex editor at the XML reveal is really there?

I guess that's one way to get your post count up quickly.

The Oracle Enterprise stage is the only one native to the Parallel engine.

Walter, you *do* know I posted that well before we had any idea what was going on, yes?

Give'em hell, Harry.

An 'alphanumeric' field means what in your job - exactly what datatype are these fields?

Wow... so that was why it was taking so long to bring up the Home page.

Much more snappier now. Setting up a separate page for information of that information sounds like a good idea to me.

Just add it at the end of the query.

Post your syntax.

That would be the COUNT.SUP that Ray mentioned.

'Trim, convert and other functions' should work just fine. Have you followed Arnd's advice?

Will you get the following output? No. Argh! It always helps to give as complete a description of what you need to do as possible from the beginning. It will cut down on the amount of thrashing people trying to help you will go through. Your examples show that neither of the two techniques I listed...

Cool, thanks. I thought it might be one of those 'one word' style dealios ala 'DET.SUP'.

Double-click on the routine to examine the source code. You'll need to use the 'Concurrent' version instead if others will be needing sequences for the same table at the same time.

Which will allow you to read them and thus they will no longer be 'bad'. You can still check the field for terminators after the fact and logically reject them if you like.