There are a couple of things you can do to alleviate the "list too long" issue.
1) If your list can be split up into logical groups, you can implement a hierarchical value list, where the user chooses first a group, then the particular value within that group. One extra step, but does cut down on the finger-swoosh shuffle.
2) You can implement a list view selection, where you take the user to a list view with the various selections. Tapping the correct value takes the user back to the previous screen with the appropriate value held in a variable (usually), to be inserted into the appropriate field. This can be enhanced with a global search field that can cut the size of the list down to something manageable.
I particularly recommend Mike's option #2, as list views in GO scroll really fast when needed, and it's an interface which doesn't give the feeling of obstructing the user's view of what they are trying to do.
Thank you very much for taking the time to reply. Both of those ideas, as well as others, I had already thought of but was trying to keep the number of steps/layouts down based on the client's request. I was just hoping someone would say, "Oh, you just need to change this setting" and then I could reply with "Duh! I should have thought of that!" Unfortunately, I was afraid the answers would be, "You need to create a work around". But, thanks for the reply and I will see what the client prefers when we discuss these anomalies!