I've written code to do exactly that. One of the consequences of this
"brute force" method of checking every possible combination of numbers
is that as the pool of numbers increases by one the number of
combinations doubles. This is fine and grand when the pool is twenty
numbers, but the jump from 24 numbers in the pool (roughly 16.8 million
combinations) to 25 numbers (about 33.5 million combinations) causes
the processing time to increase.

What is your application? This software is not ready for prime time in
terms of saleabililty, but I'd be happy to run it for you on a one-ff
basis. Contact me at cyclezen AT yahoo DOT com.