LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Losing data when importing excel into an array

Hi,

I have been writing some code that imports data from an excel .xlsx worksheet file containing 890 columns and 150 rows.

When I set the VI to import 702 columns everything works fine.  When I try to import 703 columns I get no data in my array.  The VI continues to run without any errors just gives me no results as there is no data in the initial array.

Can anyone tell me if there is a setting somewhere Im missing or explain why this is happening as I have read that there should be no limit to the amount of columns you have as long as you have less than 2^32 elements which I am well below.  I am using a Labview 2009 and a PC with windows7 64bit and 4G RAM so there should be no problem with PC resources.

Thanks,

Ray.

0 Kudos
Message 1 of 6
(2,418 Views)

Hi Ray,

 

702 is the limit when you use just 2 chars for the column name: "A" to "ZZ" allows for 702 columns.

 

Probably a subVI somewhere deep in your Excel loading routine is limited for that naming scheme (or is only aware of  older Excel versions)...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 6
(2,412 Views)

LabVIEW 2009 and MS Office 2010.  Sounds like you should updade the LabVIEW version


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 6
(2,402 Views)

RayCr,

 

Take a look at this snippet on the Excel board.  Should allow you to grab everything and then let you decide in LV what you need.

0 Kudos
Message 4 of 6
(2,401 Views)

I work in medical applications so using the latest versions is not always the answer due to the validation we need to perform on new software packages.

I currently work with version 8.6 to 2013 depending on the project.

To convert this project to 2013 would mean a validation process that would take several months to complete.

Easier just to fix the problem in 2009 and move on.

0 Kudos
Message 5 of 6
(2,379 Views)

Thanks guys I have figured out a workaround.

If I save the excel file as tab delimited rather than .xlsx and use that everything works ok.

Thanks for your input.

 

0 Kudos
Message 6 of 6
(2,378 Views)