grail, thanks for the ideas and the code correction. I've not posted must here on this site even though I've been a member for years.
Concerning the find command, I always thought you should quote the patterns, but I tried it both ways and checked the man page. The find man page states that "Please note that you should quote patterns as a matter of course, otherwise the shell will expand any wildcard characters in them."
Now with that said, I did try without quotes, but had to escape out the wildcard symbols as well when NOT using the quotes. Otherwise find returned this message:
find: paths must precede expression: some_file_name.txt
This is what appeared to work fine at the command line, not using my little $Crit junk idea:
find . -type f -name \*\.txt
I purposely escaped out the period just to ensure I do find a file with a '.txt' extension and not something like '*btxt' or what not.
I've tried different variations but the previous solution with "set -f" appears to be best so far.