DOS commands and batch files can be run from VBA with the Shell command.
The FOR command is just one of many ways to deal with importing text files that don't completely fit the Access import spec system. As a DOS devotee from the days when that is all we had, I used it until I learnt how to read and parse text files as Dave's option (b). Dave's option (a) is good if the structure of the file allows it.
I have some quite complex imports that include steps like identifying the report version from the header and processing accordingly. Some require reconnecting wrapped lines, adding extra fields, converting values etc. So I read the text file line by line, parse it and manipulate the values in code as they are written to a recordset.
Tables store the conditions which are applied to accept or reject lines with certain strings in particular locations, strings that incidate where to start parsing, when to stop parsing etc. This is a very powerful way to manage converting text to fields.
It was complex system to set up but it supports everything from the simplest to the most complex so I use it for everything in preference to the Access spec system. Moreover it supports imports to SQL server too.
I most cases I don't actually import the values to tables but load them into fabricated ADO recordsets for display in a form or report or export to Excel workbooks. (Where I work, all the reports coming from the Unix system are stored as text files and staff need them more conveniently presented.)
The recordset field specifications and value conversion information is also held in tables.