Unable to add sub-extractor pattern to existing pattern

OK. Solved the issue. When a pattern match does NOT occur, the variable will not show in the column if one clicks on the "Apply Pattern". I was expecting the column and a null value. Hope this helps anyone else in the same predicament.

Hi,

I have also sent this through the "contact us" method.

I have an existing script that works just fine. I am trying to add an additional sub-extractor pattern to my existing extractor/sub-extractor pattern (5 subs already); however, SS does not show up the new sub-extractor pattern in my "apply pattern". Everything else looks normal (the pattern is in sequence and parameter is defined). Not sure what's going on.

The only change that has occurred is that I have just switched from trial to paid professional. I had some trouble registering (SS would not accept my email). After going back and forth, I emailed Todd my resource/db/files and he manually registered the software, emailed it back, and I copied it over (it works).

Thanks.
N

Screen-scraper uses a

Screen-scraper uses a HashTable, as opposed to the newer HashMap for the dataRecord object, which doesn't allow null keys or values.