No, (for DOS expressions/paths), only folders end with \
As per the Help
4. Folder names end with a backslash, whereas files do not, e.g. \My Documents\ and \My Documents\filename.txt
Any component of a relative path (which is all our filters & de/selections are working with) is assumed to start with a \ and this convention is used to signify that the immediate-next character is the start of a new component (file or folder) name.
* means zero or more characters
so
*\*.db
means a file called something.db anywhere (whether in a subfolder or not, because * can mean 'no preceding characters at all'). The \ doesn't indicate the end of a folder, it indicates the start of the following name (and if it does not end in \ it represents a file; if it does end in \ it represents a folder)
Bear in mind that we may need something to tell us where the name starts. Otherwise
*ion.doc
as a filter entry would match the path
\ion.doc
fine, yes (if you were interested in ions, maybe), but it would also match
\application.doc
because we have nothing to say where the wild-card-matching should stop. That's what the leading \ does (if used)
Bear in mind exclusion filters are applied after inclusion filters (and trump them, if any conflict). Thus, exclusion filters do not need entries to tell them which paths to search (the inclusion filters have already controlled that part). Ipso facto, the inclusion filters do need at least one 'which path(s)?' entry, either separate, or included in another entry. You would generally include
*\
which means 'look inside any path' (anything ending in a backslash), hence any/every relative path. Unless you want to restrict it to certain paths, in which case you need to omit *\ and instead add appropriate entries to control that. As per the examples in the Help.
As per the Help
4. Folder names end with a backslash, whereas files do not, e.g. \My Documents\ and \My Documents\filename.txt
Any component of a relative path (which is all our filters & de/selections are working with) is assumed to start with a \ and this convention is used to signify that the immediate-next character is the start of a new component (file or folder) name.
* means zero or more characters
so
*\*.db
means a file called something.db anywhere (whether in a subfolder or not, because * can mean 'no preceding characters at all'). The \ doesn't indicate the end of a folder, it indicates the start of the following name (and if it does not end in \ it represents a file; if it does end in \ it represents a folder)
Bear in mind that we may need something to tell us where the name starts. Otherwise
*ion.doc
as a filter entry would match the path
\ion.doc
fine, yes (if you were interested in ions, maybe), but it would also match
\application.doc
because we have nothing to say where the wild-card-matching should stop. That's what the leading \ does (if used)
Bear in mind exclusion filters are applied after inclusion filters (and trump them, if any conflict). Thus, exclusion filters do not need entries to tell them which paths to search (the inclusion filters have already controlled that part). Ipso facto, the inclusion filters do need at least one 'which path(s)?' entry, either separate, or included in another entry. You would generally include
*\
which means 'look inside any path' (anything ending in a backslash), hence any/every relative path. Unless you want to restrict it to certain paths, in which case you need to omit *\ and instead add appropriate entries to control that. As per the examples in the Help.