The only other thing that could be in the way is the size of the table and the nature of what you are importing.
Last I looked, Excel limits its cells to 255 bytes but doesn't enforce a record length because Excel isn't record-oriented. It is entirely cell-oriented. (Proof: rows and/or columns can be sparsely populated and cells within either can have independent formats.) A .CSV file doesn't have a relatively low record sizing limit if I recall correctly. Lines can get pretty big. Basically it is a data stream file usable by C++ with variable length records.
If you have a lot of long text fields, you might be running into a record sizing problem. If your text fields lead to a record length that would exceed 2K bytes, I think you are hosed on a direct import. For 36 columns, that would be an average of 55 or 56 bytes per field.
Are you importing a bunch of long text fields?
In that case, you might NEVER import that data because Access limits record lengths pretty severely. Give us a few more details about record sizes, field counts, etc, and we might be able to figure a workaround. But from where we sit, we are obviously having trouble figuring out what is going on.