Regular expressions are very literal. So if you don't specify there is a newline character between the "Order#" and the number, Pattern Matching will reject anything with a newline character in between.

^.+ is basically saying "everything after the beginning of the input (white space or non-white space characters), so it is including the newline character and getting everything.

Try: Order#\s*\n(\d+)

I thank you both for your quick response.  Unfortunately neither worked.  Logic says and another Reg Editor I used says Order#\s*(\d+) works, but as you can see here it does not.  I tried ther \D?\D? to no avail.  The problem may be that I am not using a token.  As you can see I am RE a field directly.  Is this a problem?  I will go back and create a token but this seems like an extra step.  Also, this does NOT work in WF either.  I tried to test it by putting a Routing Activity into a new WF and then opened the Token Dialog box for a Date field (looks just like the attached screens).

Bob

Kenneth, from the looks of your dialog box it appears you are using an 8.x version of QF.  Mine is 9.0.0.  That may make a difference

Kenneth,

I was given two solutions, so was trying both.  There is no space between Order & #.  It looks that way, but is it not there.  I am certain of all the characters as can be seen in this attachment.  Also attached is a WF token editor where \D*? does not work.  I have a rebooted machine and no Virus scanner on.  I can't use a multi index field as I have a number of these to fill in and I can not always be sure it will be the 2nd or 3rd row.  Thanks for any other suggestions you might have.

Miruna,

I think it is something wierd.  I opened a new session also.  Attached is my latest screenshot per your suggestion and it does not work on my machine.  I have spend a number of hours on this trying many different things to no success including \r\n

Kenneth

Not sure what you mean by modifying inside QF.  That is what I have been doing.  Have tried this inside QF regardless of what token editor said and it did not work.  Please expand on your thoughts.  Thanks

Kenneth

Got it working.  Will report the bug to support.  Comforting to know two of us get the same thing.  Thanks for your help

Kenneth

What would never work in any of the test facilities, but worked fine under running/scanning circumstances was Order#\s*\n(\d+) .  I did 6 other fields with variations of these.  \x0D\x0A would NOT work which baffles me.  I did not go back and try your suggestions \D?*, but will later today as it should work, but the more I read on the MS page, the more special \n is treated and this is the point Miruna was trying to make yesterday that \n has to be dealt with on its own.  The rest of the characters see to do fine apparantly.  Thanks again for your help

Miruna,

I don't understand. \x00 comes right out of the list of valid character escapes on both QF and WF.  What would be the proper way to use a character escape then in reg exp?

Miruna

Open up the Token Window in either QF or WF, pick any vaiable like Date, check Regular Expression box and then click on the pattern button on the right and they character classes.  Also there is the help file

Character Escapes

Most regular expression language operators are unescaped single characters. The escape character \ (a single backslash) signals to the regular expression parser that the character following the backslash is not an operator.

Example: The parser treats an asterisk (*) as a repeating quantifier and a backslash followed by an asterisk (\*) as the Unicode character 002A.

Note: The character escapes listed are recognized both in regular expressions and in replacement patterns.

So can you tell me why \x0D\0A does not work?  Tks 

Oh, I see, sorry about that, not sure how I missed it. They're not being read as a group (like i mentioned, regex is very literal). They're read as "\x" and other characters. You need to wrap them in a non-capturing group, "(?:)", to get them to be considered together.

Order#(?:\x0a)*(\d+)