This is happening with every export job I've created in v2019.  I specified a comma delimiter on the Configuration tab of VI.  My export files all have an extra comma at the end of each row.  For example:

AC,XXX01,2018,01,1A,2G,0,

PS: What's wrong with exporting with VI?

This is happening with every export job I've created in v2019.  I specified a comma delimiter on the Configuration tab of VI.  My export files all have an extra comma at the end of each row.  For example:

AC,XXX01,2018,01,1A,2G,0,

PS: What's wrong with exporting with VI?

I use crystal reports or custom lookups and export to excel over VI exports.

Most use other programs such as Access or Excel to PULL data as it is lots faster and gives you greater control.  Access is up to 10 times faster pulling data compared to VI.   I would not worry about a single comma at the end.

VI Exports are awkward and limited.  If a VI job works for your needs, great.  Other options (with some good alternatives listed already) are more flexible for sure. 

In addition to the suggestions others have posted, VBScript is effective too (through ODBC), with excellent control over the formatted output.