It will depend on your specific use case as to whether or not this will work for you, but in the past where we have needed the end users to control which files can or need to be loaded we would just store this list of files to be loaded in an Excel "configuration" file. The users can then just update the Excel configuration file to specify which files should be loaded, which types of data, and from where. The QV load script then just loads the list of files from the Excel configuration file and processes them one by one. Depends on your specific use case as to whether or not this approach will work for you, but this has worked well for me in some situations where we need to load multiple files into a single application, and the list of files is being managed centrally by a business user.
