Sage 100

I've had intermittent issues with XLS / XLSX files as a VI data source over the years, and haven't nailed down the error patterns, but two things I do know:

• Excel needs to be installed, with an active Excel license, before it can work.
• Multi-tab spreadsheets can cause problems.

yeah, csv is always safest.

I've had intermittent issues with XLS / XLSX files as a VI data source over the years, and haven't nailed down the error patterns, but two things I do know:

• Excel needs to be installed, with an active Excel license, before it can work.
• Multi-tab spreadsheets can cause problems.

When I am generating the file, I try to go with a non-standard separator like "^", so I don't need to do anything special for commas as data... but if saving from Excel, yes, CSV is often reliable.

yeah, csv is always safest.

I've had intermittent issues with XLS / XLSX files as a VI data source over the years, and haven't nailed down the error patterns, but two things I do know:

• Excel needs to be installed, with an active Excel license, before it can work.
• Multi-tab spreadsheets can cause problems.

I always use tab separated values.  It eliminates the risk of a CSV that doesn't have descriptions with commas enclosed in quotes.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Is VI recognizing quoted commas now?  In my experience, VI treats commas wrapped in double-quotes as a separator, not data... but it has been a while since I have even tried.

Edit: Tab separated is also a good strategy.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 05-05-2026 11:50
From: Doug Higgs
Subject: Importing from Excel file

I always use tab separated values.  It eliminates the risk of a CSV that doesn't have descriptions with commas enclosed in quotes.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

For tab separated check the "Use ACSII Delimiter" box in VI then use 009 as the value.

Is VI recognizing quoted commas now?  In my experience, VI treats commas wrapped in double-quotes as a separator, not data... but it has been a while since I have even tried.

Edit: Tab separated is also a good strategy.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-05-2026 11:50
From: Doug Higgs
Subject: Importing from Excel file

I always use tab separated values.  It eliminates the risk of a CSV that doesn't have descriptions with commas enclosed in quotes.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

Thanks, @Doug Higgs for not making me look that up. I've used various delimited files before but I was trying to make this easier for the end user, and not make them have to Save As.  But looks like I'll just have to tap dance harder at how EASY IT IS TO SAVE AS (I know, but you also know how some Nervous Nelly end users are).

For tab separated check the "Use ACSII Delimiter" box in VI then use 009 as the value.

Is VI recognizing quoted commas now?  In my experience, VI treats commas wrapped in double-quotes as a separator, not data... but it has been a while since I have even tried.

Edit: Tab separated is also a good strategy.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-05-2026 11:50
From: Doug Higgs
Subject: Importing from Excel file

I always use tab separated values.  It eliminates the risk of a CSV that doesn't have descriptions with commas enclosed in quotes.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

I also find that Calc from OpenOffice is better at letting you set whatever delimiter you want when saving from .xlsx to .csv.

Thanks, @Doug Higgs for not making me look that up. I've used various delimited files before but I was trying to make this easier for the end user, and not make them have to Save As.  But looks like I'll just have to tap dance harder at how EASY IT IS TO SAVE AS (I know, but you also know how some Nervous Nelly end users are).

For tab separated check the "Use ACSII Delimiter" box in VI then use 009 as the value.

Is VI recognizing quoted commas now?  In my experience, VI treats commas wrapped in double-quotes as a separator, not data... but it has been a while since I have even tried.

Edit: Tab separated is also a good strategy.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

I also find that Calc from OpenOffice is better at letting you set whatever delimiter you want when saving from .xlsx to .csv.

Thanks, @Doug Higgs for not making me look that up. I've used various delimited files before but I was trying to make this easier for the end user, and not make them have to Save As.  But looks like I'll just have to tap dance harder at how EASY IT IS TO SAVE AS (I know, but you also know how some Nervous Nelly end users are).

For tab separated check the "Use ACSII Delimiter" box in VI then use 009 as the value.

Is VI recognizing quoted commas now?  In my experience, VI treats commas wrapped in double-quotes as a separator, not data... but it has been a while since I have even tried.

Edit: Tab separated is also a good strategy.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-05-2026 11:50
From: Doug Higgs
Subject: Importing from Excel file

I always use tab separated values.  It eliminates the risk of a CSV that doesn't have descriptions with commas enclosed in quotes.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

Not sure if it makes a difference, however, in Excel I always click File, Export, Change File Type, Tab Delimited.  The "Save As" option may work the same.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 05-05-2026 14:13
From: Calvin Morrison
Subject: Importing from Excel file

Original Message:
Sent: 5/5/2026 2:11:00 PM
From: Phil McIntosh
Subject: RE: Importing from Excel file

I also find that Calc from OpenOffice is better at letting you set whatever delimiter you want when saving from .xlsx to .csv.

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 05-05-2026 13:19
From: Beth Bowers
Subject: Importing from Excel file

Thanks, @Doug Higgs for not making me look that up. I've used various delimited files before but I was trying to make this easier for the end user, and not make them have to Save As.  But looks like I'll just have to tap dance harder at how EASY IT IS TO SAVE AS (I know, but you also know how some Nervous Nelly end users are).

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 05-05-2026 11:57
From: Doug Higgs
Subject: Importing from Excel file

For tab separated check the "Use ACSII Delimiter" box in VI then use 009 as the value.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 05-05-2026 11:53
From: Kevin Moyes
Subject: Importing from Excel file

Is VI recognizing quoted commas now?  In my experience, VI treats commas wrapped in double-quotes as a separator, not data... but it has been a while since I have even tried.

Edit: Tab separated is also a good strategy.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-05-2026 11:50
From: Doug Higgs
Subject: Importing from Excel file

I always use tab separated values.  It eliminates the risk of a CSV that doesn't have descriptions with commas enclosed in quotes.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

Been using Tab-separated TXT to save Excel for 20+ years.  Has eliminated a LOT of VI import stress.

Not sure if it makes a difference, however, in Excel I always click File, Export, Change File Type, Tab Delimited.  The "Save As" option may work the same.

I also find that Calc from OpenOffice is better at letting you set whatever delimiter you want when saving from .xlsx to .csv.

Thanks, @Doug Higgs for not making me look that up. I've used various delimited files before but I was trying to make this easier for the end user, and not make them have to Save As.  But looks like I'll just have to tap dance harder at how EASY IT IS TO SAVE AS (I know, but you also know how some Nervous Nelly end users are).

For tab separated check the "Use ACSII Delimiter" box in VI then use 009 as the value.

Is VI recognizing quoted commas now?  In my experience, VI treats commas wrapped in double-quotes as a separator, not data... but it has been a while since I have even tried.

Edit: Tab separated is also a good strategy.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-05-2026 11:50
From: Doug Higgs
Subject: Importing from Excel file

I always use tab separated values.  It eliminates the risk of a CSV that doesn't have descriptions with commas enclosed in quotes.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles