main vs sub extraction
I couldn't find an answer to this, but it should be a simple answer. Is it better to have multiple 'Main' extractor patterns OR 1 'Main' and multiple sub-extractor's beneath?
I'm finding the CSS
tables change "position" or don't even exist in one page scrape vs the next; this is far from a normal site. :)
main vs sub extraction
Ryan,
We weren't aware of a particular size limitation with regards to the DATARECORD token. If you could provide us with an example of where you've encountered this limitation it would be appreciated.
If we're able to verify a memory ceiling for the DATARECORD token we will work on a fix for it. In the mean time, you can try to increasing the overall memory allocated to screen-scraper. To do this within the workbench go:
Options > Settings > Maximum memory allocation...
Please let us know,
Scott
main vs sub extraction
Todd answered this, however there is a limit on the size of the DATARECORD captured in a main extractor and thus the sub-extractor is unable to parse anything from the main. *sigh*