I think the issue may be that it's trying to use Unicode. I don't know if it's connected, but the older versions of GoldMine that used dBase as the back end couldn't use Unicode. The BDE didn't like it. If your data is in English, saving it with the older character set should be fine because the normal characters all match up. It's only after the line feed / carriage return that things get different. And that may be why your data has the headers moved around.
If you have a lot of special characters or characters from different alphabets, then I'd suggest keeping it as a CSV and importing it into a Unicode table via SQL.
We use a combination of Excel and Access to convert to dbf without any issues these days.
Thank you and I continue to have the same problems. I also have Access with my O365 subscription, but I just don't know what I'm doing wrong.
I believe it has something to do with the character set.
I will update this thread after the weekend and I give it a little more effort.
Have you considered simply using the CSV directly?
Granted, CSV is an awful format akin to punched cards for all its ability to scramble data, mis-interpret any sort of special characters and so on, but, GoldMine does have the ability to import a well-formed CSV via its own import wizard.