I would double check the apostrophes in the JRNLDESC field in case you missed one.

Rows 54, 59, 100, 108, 121, 127, 277, 283, 411, 421 (in your Excel file) contain apostrophes in the  JRNLDESC field.

Also - it might not hurt to do the same check for GLBTCL.BTCHDESC.

Thanks, Shane.
I tried replacing the fields in both tables but the error still persists.
The original data is from Sage too so I can't figure out where the error is since Tim has also loaded the data and it worked in his setup. 

Thanks, Shane.
I tried replacing the fields in both tables but the error still persists.
The original data is from Sage too so I can't figure out where the error is since Tim has also loaded the data and it worked in his setup. 

Hih@AIT could you send me your ODBC details by running the following Powershell script?

Get-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources\' |
ForEach-Object {
$dsnName = $_.PSChildName
$driverName = $_.Driver

$driverPath = $_.'Driver32'

$attributeValues = Get-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\$dsnName\"

Write-Host "DSN Name: $dsnName"
Write-Host "Driver: $driverName"
Write-Host "Driver Path: $driverPath"
Write-Host "Attributes:"

$attributeValues | Get-Member -MemberType NoteProperty | ForEach-Object {
$attributeName = $_.Name
$attributeValue = $attributeValues.$attributeName
Write-Host "- ${attributeName}: ${attributeValue}"
}

Write-Host "----------------------"
}

Hi Shane,
Here's the info requested.
I didn't use ODBC since the SAGE setup is via direct SQL as per Tim's sample.

___________________________________________

DSN Name: ODBC Data Sources
Driver:
Driver Path:
Attributes:
- PSChildName: ODBC Data Sources
- PSDrive: HKLM
- PSParentPath: Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI
- PSPath: Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources\
- PSProvider: Microsoft.PowerShell.Core\Registry
- WIN7SP12018: SQL Server Native Client 11.0
- Xtreme Sample Database 11.5: Microsoft Access Driver (*.mdb)
----------------------

Just a note when you use the "Server" option in Database Setup it still uses ODBC, it just uses a Native Client that allows you to connect to all databases though a single DSN.  If you select "Data Source" you have to create individual ODBC DSN's for every database.  So don't ever delete your DSN connection thinking you don't need it