If you have a calc field defined as Get(RecordNumber)
you can enter find mode,
set that field to <101
and constrain found set.
Note that this can be done manually or can be scripted.
Note also that which 100 records you find will be dependent on the current sort order. If you resort, which records have which record numbers may change. If this is important, I would script the action and build in the desired sort step before the find step.
Is this what you're after, or are you looking for something more specific?
Note also that which 100 records you find will be dependent on the current sort order.
I don't think so: I believe it will always find the first 100 records in creation order.
Why not simply go to record #101 and omit Get(FoundCount)-100 records - no calculation field required.
Doggone if comment isn't right.
My mock-up was not thorough enough, I appreciate the correction.
I just mocked it up more rigorously and proved myself wrong (and comment right...big surprise there ;) )
Thanks for jumping in and teaching us both.
When I constrain the find is says no records match. When I put the less than with a number in the Get(RecordNumber) field and do not constrain the find it retrieves that number but it disregards the found set and retrieves the records from the beginning of the entire record list instead of the found set list.
Are you saying go to record 101 in the found set? How do you do the omit Get(FoundCount)-100 with out a calculation? Does this result in retrieving 100 of the found set of records?
Look at the Omit Multple Records  script step.
I was able to do this manually and should be able to include this script step in a script and hopefully automate this process. I appreciate your taking time to help me. Thank you.