Sorry, I should have been more clear, in how I was doing it. I am using V/I to export the data via the ODBC. Unfortunately the linked table or import to access via access natively wasn't an option in my use case. I did through trial and error solve my issue. I started over and setup a new table with all fields as short text, limited the field names to 8 characters or less and limited the number of fields I was pulling from both PO header and detail, where originally I was pulling all fields from both in case they wound up being needed later.  My gut tells me it was a combination of the 3 things, but once I had what I needed it didn't feel like testing the number of fields, but in case someone reads this later, I figured I would include the information. Thanks to all who tried to help!.

Sorry, I should have been more clear, in how I was doing it. I am using V/I to export the data via the ODBC. Unfortunately the linked table or import to access via access natively wasn't an option in my use case. I did through trial and error solve my issue. I started over and setup a new table with all fields as short text, limited the field names to 8 characters or less and limited the number of fields I was pulling from both PO header and detail, where originally I was pulling all fields from both in case they wound up being needed later.  My gut tells me it was a combination of the 3 things, but once I had what I needed it didn't feel like testing the number of fields, but in case someone reads this later, I figured I would include the information. Thanks to all who tried to help!.

VI exports are very awkward and the alternatives are plentiful, more flexible, and easier to work with.

Agreed, and I usually avoid them at all costs, but it gets the job done for this project which had very specific requirements. The good news was I got it working and the customer has what they need.