|
Sorry about that. Yes, the '*' is the wildcard. '*.xls' was what I was using for an example. It would also have to work for things like 'info*.xls' and '*info.xls'. The users are entering these 'patterns'.
I will have to try adding logic to drop the wildcard if it is in the first spot. Actually I am even having trouble getting the QCLSCAN to return a "found" for the pattern of '0*.txt' in a string of '001Test.txt' using the '*' as a wildcard. Back to playing with it....
-- Thanks, Scott J qsrvbas@xxxxxxxxxxxx wrote:
midrange-l-request@xxxxxxxxxxxx wrote:7. Alternative to QCLSCAN? (Scott Johnson) Is there an alternative to the QCLSCAN API? I need to scan incoming filenames from the readdir IFS API for matches to things like "*.xls". QCLSCAN does not allow the "*" in the first spot.I'm confused... what "first spot"? I can call QCLSCAN with a string that has '*' in the first character and with a search pattern with '*' in the first character. Either will return the correct position. Can you give a more complete explanation? Are you wanting to use the '*' as a wild-card? If so, why not scan for ".xls" instead and leave the '*' off? Tom Liotta
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.