DSXchange

I'm curious what the 'work around' is... everything here (so far) is a proper solution in my mind. What did you try? Do you still need help?

Good. It's not uncommon for things that 'worked' in older versions to stop working in newer ones as they tighten up code or address bugs for things that never really should have worked in the older version. Can you please mark the thread as Resolved using the big button at th top of the screen? Than...

This is the second time you've jumped on the end of someone else's barely related thread asking about this. If you really want to start a dialogue on this subject, please start your own post.

The first 'problem' I see is three dates in two different formats:

last_trans_dt = 02/20/2009
e_opt_in_date = 06/07/2009
last_maint_dt = 2009-06-09

You need to be consistent.

I didn't mean address the issue directly, thought maybe there might be a useful nugget of information buried in there somewhere. Guess not.

So... are we starting a FAQ on the subject?

*Note: Topic Relocated from FAQ forum - Content Editor*

Using a hex editor or a dump of the file ("od -x") can you ascertain what the actual underlying hex values of those characters are?

You need a stage variable that is set once and then not touched again after the condition is found to use as your constraint in your main link. Initialize it to a value (say 0) and when your condition is found and it is still 0 set it to 1 else set it to itself. Then you can treat it as a boolean in...

This help at all? http://ourldsfamily.com/mypapers/unhangterm.html

Aye, noted that in the first post Matey.

nagarjuna wrote:Can anybody test a simple job with pivot stage and giving one of the field as BIGINT in output and input of pivot stage ?

A version 8 job, I assume... 8 dot what?

Aarrgh? I didn't realize it was Talk Like a Pirate Day again already.

While both are good resources, the latter is more on topic here as an 'operator' is a different animal than a custom routine.

As an online tutorial reference option, ->this site<- was recently mentioned in another forum and looks to be fairly complete. Note that's for Server, there's a link at the bottom of that page for the "Enterprise Edition" a.k.a. PX jobs that looks like it still needs to be fleshed out quit...

Which 'Compilation options' do you have checked in the Sequence job? How are you ensuring it aborts when there are warnings? What triggers are you using between jobs? Need more details.