I examined your sample and there are cases where you will have a LOT of NewLines in the table cells. Some of those cells are HUGE, text-wise, and could not possibly be imported as anything but a LONG TEXT field. My question to you is, have you considered importing from Word first and then removing extra CR/LF (or just LF) characters? Might be easier. And there is then the question of what you intend to do with the imports, because unless you enable RTF in the fields, you will lose the bullet-points too.
You could do this either from Word (using a Macro) or Access (using VBA). IF you use Access, you could do it BEFORE importing everything by specifying the table number, row number, and column number as CurrentDocument.Table(x).Row( y ).Cell(z) but I'm not sure what doing it early would do with the import process. Doing it AFTER you import, you would be using Access RecordSet operations one field at a time. You would not need to create and manage a Word Application Object in that case.
I'm not sure which way you want to go, but I would personally favor doing the import and then coming back to clean up the Access mess. Less likely to mess up the import process, to my way of thinking. But depending on your actual requirements, might be the wrong approach. I can't tell from here.
